Q. So what's the difference between "Host" volumes and Bind Mount ? Thank you for sharing your knowledge. It is helping me a lot. Especially the practical examples and use cases.

@headintheclouds.online

2 ай бұрын

That’s a great question, thanks for your comment! 🙌🏻 Host volumes are managed by Docker and stored in a dedicated location on the host such as ‘/var/lib/docker/volumes/’. They’re easier to use and more portable since Docker handles their creation and management. Bind mount volumes on the other hand directly map a specific host directory to a directory in the container. This gives more control and flexibility, which is useful for development or when you need direct access to the files on the host. In a nutshell: host volumes are best for general persistence, while bind mounts are ideal for situations like having a specific host paths. You are very welcome! We’re here to grow together 🌱☺️

@richthekid7522

Ай бұрын

Thanks so much for the docker series, learnt alot!. I hope you can also touch on other tools in the future 😊

@headintheclouds.online

Ай бұрын

You are very welcome! Really pleased to hear that 🤗 We’re currently working on Kubernetes series so stay tuned for more! 🚀

It looks like the best place to store things like connection strings for external databases and configuration is in a "Bind Mount", is that correct?

@headintheclouds.online

2 ай бұрын

Thanks for your message! ☺️ Using a bind mount might seem convenient, however it's not the most secure option out there. Instead, consider leveraging Docker secrets or env variables to keep your data safe and sound 🔐