Docker Compose Bind Mount or Volume with DO Volume says “Bind Mounts” are inferior to “Volumes”. But volumes run on the host machine’s disk, not the DO Volume.

Changing the Docker “data root” could move all things Docker to the DO Volume, but I worry about a) persisting unnecessary data and b) running two hosts from the same data root.

What’s the best way to persist a docker-compose.yml app’s data on a DO volume?

Thank you!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there @digitalocean457,

One option would be to follow the steps here on how to attach DigitalOcean Block Storage to Docker container:

The main thing to consider in this case is that block storage can only be mounted to 1 Droplet at a time. If you have a docker swarm and you need to mount the volume to multiple droplets, as mentioned by one of the users in that question, you could use GlusterFS as a replacement solution instead.

Hope that this helps! Regards, Bobby