@aschmelyun A bit of a warning here. Care should be taken when explicitly specifying the --volumes option with docker system prune.

Recent changes to the Docker API have made it even harder to unintentionaly lose volume data, since pruning volumes now defaults to only affecting anonymous volumes which are not used by any container at the time of pruning and volume pruning through docker system prune was disabled by default.

However, by explicitly specifying --volumes as an option to docker system prune this protection is circumvented and it's entirely possible to lose data persisted by Docker volumes which are not used by any container at the time of performing the pruning operation.

The recommended solution to avoid this issue is to always use labels, either as part of docker client requests (docker run etc.) or inside Docker compose configurations, and then filter them out by using --filter in combination with operations such as pruning etc.

As silly as this all might sound it can be the cause for some serious loss of data, which I can personally attest to, unfortunately 🤷

Create a Simple Dockerfile