> I've never quite understood this pattern. It's a pattern that dates from when nobody really knew how to handle persistent storage with containers. The idea w

> I've never quite understood this pattern. It's a pattern that dates from when nobody really knew how to handle persistent storage with containers. The idea was that you could then move the data around using only the docker api I guess? I've seen it become 'best practice', and then disappear again in favour of "volumes" - which imho are just as useless, and failed to see the bigger picture. When running 'non-cloud-native' applications in docker-containers on snowflake servers, it - in my opinion - is indeed better to just map a local folder into the container, with docker-compose you can specify one relative to the docker-compose.yml file location, which makes this even more attractive. On k8s, you have storage providers/volumes/pvcs that attempt to address these needs, but I'm still a proponent of storing your data outside a k8s cluster as much as possible, and nothing that needs persistence should be stored in the containers, unless these are cluster-aware and handle their own clustering/replication and data storage.