Docker Volume Driver for DigitalOcean
Visit siteDocker volume driver to consume DigitalOcean volumes in Docker containers.
The driver is based on the Docker Volume Plugin framework and it integrates DigitalOcean’s block storage solution into the Docker ecosystem by automatically attaching a given block storage volume to a DigitalOcean droplet and making the contents of the volume available to Docker containers running on that droplet.
by: Ovidio MalloNovember 16, 2016Visit site
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!
Publish your Tool on Community
Have you created an Integration, API Wrapper, Service, or other Tool that helps developers build on DigitalOcean? Help users find it by listing it in Community Tools.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Refer these for up-to-date solution: https://github.com/rexray/rexray/blob/master/.docs/user-guide/storage-providers/digitalocean.md#do-block-storage https://medium.com/@adrian.gheorghe.dev/docker-swarm-volume-data-persistence-on-digital-ocean-with-rexray-cd418f718131
I’d also really like to know the benefit of mounting the volume directly to the container over mounting to the droplet and creating a volume from there.
I tried this because I am having some issues writing to the volume mounted to my droplet from running containers. This didn’t fix the problem (still unresolved) but did lead me to ask the question above…
If anyone has any advice regarding my write issue, I’d be SUPER grateful. Basically, I can write to the volume from the droplet (obviously), I can write to it from the container (as root), but all containers are having problems writing to it from their running services (eg. apache, atmoz/sftp).
I assumed a permission/ownership issue, but I think I’ve tried every combination under the sun. Also, if I swap the target of the docker mounted volume so something else on my host droplet (ie something that is not mounted), it works fine.
Thoughts?
Thanks for the plugin Ovidio! I had an issue using it so I filed the details here: https://github.com/omallo/docker-volume-plugin-dostorage/issues/8.
One general question though: What advantage do you see of using this plugin over mounting the volume and then running a Docker container using a host mounted volume that resides within the docker volume in the filesystem?
Thanks for the plugin Ovidio! I had an issue using it so I filed the details here: https://github.com/omallo/docker-volume-plugin-dostorage/issues/8.
One general question though: What advantage do you see of using this plugin over mounting the volume and then running a Docker container using a host mounted volume that resides within the docker volume in the filesystem?