Replies: 3 comments 2 replies
-
|
It removes anything not in use. If you remove a container, then run the scheduled prune job, it's going to remove whatever you've checked below that. So if you have everything checked it will remove everything for that container you just removed or stopped. The image(s), the volume, the network and all of the build cache arcane uses. It will be like that container never existed. I like to prune images because those take up a lot of space when a container gets updated. The other things I personally avoid. If a container goes down then you would lose everything for it. If you have a bind mount for the config files of the container then that would still be safe as well as the compose file. |
Beta Was this translation helpful? Give feedback.
-
|
Dangling vs All, All = Even tagged images that are not used |
Beta Was this translation helpful? Give feedback.
-
|
The prune setting, is used anywhere a prune is used mainly for images, and others but its rare youd even get those. I think i answered you question. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The settings are confusing a bit.
What is the Prune behavior correlation with the prune jobs?
Does it affect each other?
Additionally if I hit the Prune System in the dashboard, it also offers me all the settings.
So I'm not sure where the
Docker Prune Action BehaviorappliesI assume these are only used during Prune Job (Intuitive)

I assume these are only used on this current action that is going to happen (Intuitive)

I cannot understand where this setting applies?

Beta Was this translation helpful? Give feedback.
All reactions