You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using named volumes with docker-compose and watchtower, it won't remove named volumes with --remove-volumes argument (will only deassociate them from container) though volume contents won't be updated.
Is it possible to change this behavior and perform something like docker volume prune after container has been stopped and removed?
The text was updated successfully, but these errors were encountered:
You should be able to do this already using lifecycle hooks. For instance, you could add a script running docker volume prune on post-update. Another solution, which I tend to utilize myself, is to add a cronjob running the prune command every night.
When using named volumes with docker-compose and watchtower, it won't remove named volumes with --remove-volumes argument (will only deassociate them from container) though volume contents won't be updated.
Is it possible to change this behavior and perform something like
docker volume prune
after container has been stopped and removed?The text was updated successfully, but these errors were encountered: