Don't prune volumes on docker system prune#118
Conversation
|
Maybe make it an option? I mean system prune or any other destructive operation are not to be used if you don't know what you're doing 👼 |
|
Making it an option sounds good. |
|
+1 for an option. |
|
Yes, I think having an option could make sense, on the other hand, calling Open to both options 😊 |
|
We can add an option. THe reason I didn't is it's kind of weird with the existing "--all" option (which is just weird anyway). |
Volumes tend to carry important data and pruning them on `docker system prune` can easily cause unwanted data loss. Let's play it safe and not prune volumes on `system prune` by default, and instead provide an option. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
|
Added the option. |
vdemeester
left a comment
There was a problem hiding this comment.
LGTM 🐯
the --all option is a little bit weird. Could we (in a follow-up PR) deprecated it, hide it and renaming it to --all-images or something ? 👼
|
This didn't make it into 17.06, so updated the milestone |
…-master-f40f9c240ab03d20ae16ba97ec97ecb2cad50558 [master] sync to upstream master f40f9c2
bump version to 17.06.1-ce-rc1
Volumes tend to carry important data and pruning them on
docker system prunecan easily cause unwanted data loss.Let's play it safe and not prune volumes on
system prune.Throwing this out there.