New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker volumes docs out of date #20465

Closed
cpuguy83 opened this Issue Feb 18, 2016 · 8 comments

Comments

Projects
None yet
8 participants
@cpuguy83
Contributor

cpuguy83 commented Feb 18, 2016

The documentation for docker volumes (found here: https://docs.docker.com/engine/userguide/containers/dockervolumes/) is woefully out of date.

Since docker 1.9 includes top-level volume subcommands, and support for volume plugins, this documentation should be updated to reflect these new features.
It should also de-emphasize data-only containers as these are no longer considered a recommended pattern.

@AriaFallah

This comment has been minimized.

Show comment
Hide comment
@AriaFallah

AriaFallah Jun 7, 2016

In the mean time, where can I learn about the docker volume command and how to use it?

AriaFallah commented Jun 7, 2016

In the mean time, where can I learn about the docker volume command and how to use it?

@mabraham

This comment has been minimized.

Show comment
Hide comment
@mabraham

mabraham Jul 19, 2016

@AriaFallah https://docs.docker.com/engine/tutorials/dockervolumes/ does document at least some of the functionality of docker volume

mabraham commented Jul 19, 2016

@AriaFallah https://docs.docker.com/engine/tutorials/dockervolumes/ does document at least some of the functionality of docker volume

@EugenMayer

This comment has been minimized.

Show comment
Hide comment
@EugenMayer

EugenMayer Aug 18, 2016

At least this section needs to be updated i guess https://docs.docker.com/engine/tutorials/dockervolumes/#/creating-and-mounting-a-data-volume-container ... please notice that this already leads to issues / misconceptions like http://stackoverflow.com/questions/39013222/data-container-with-named-or-anonymous-volumes-conceptual-problems-discuss .. it would be great to get this fixed

EugenMayer commented Aug 18, 2016

At least this section needs to be updated i guess https://docs.docker.com/engine/tutorials/dockervolumes/#/creating-and-mounting-a-data-volume-container ... please notice that this already leads to issues / misconceptions like http://stackoverflow.com/questions/39013222/data-container-with-named-or-anonymous-volumes-conceptual-problems-discuss .. it would be great to get this fixed

jwhitlock added a commit to mozilla/kuma that referenced this issue Sep 23, 2016

bug 1218563: Use named volume for mysql container
Instead of a data container, create and use a named volume to store the
MySQL database.  The Docker community suggests this method, but the
Docker docs still suggest data-only containers.

http://stackoverflow.com/a/20652410/10612
moby/moby#20465

jwhitlock added a commit to mozilla/kuma that referenced this issue Sep 24, 2016

bug 1218563: Use named volume for mysql container
Instead of a data container, create and use a named volume to store the
MySQL database.  The Docker community suggests this method, but the
Docker docs still suggest data-only containers.

http://stackoverflow.com/a/20652410/10612
moby/moby#20465
@chernals

This comment has been minimized.

Show comment
Hide comment
@chernals

chernals Oct 1, 2016

Reviving this issue as I believe the present doc is quite misleading. It took me a while to understand the present-day situation.

chernals commented Oct 1, 2016

Reviving this issue as I believe the present doc is quite misleading. It took me a while to understand the present-day situation.

@p-baum

This comment has been minimized.

Show comment
Hide comment
@p-baum

p-baum May 10, 2017

I'm just picking up docker for the first time. The first thing I wanted to learn was best practices for data persistence. Finally, after being misled by dockers own documentation, I realise named volumes are the new standard. I took a lot of energy to learn that. I consider myself lucky I learned it at all. I will continue to learn despite dockers own misleading documentation. I could take some time considering all the second opinions I am now inclined to seek.

p-baum commented May 10, 2017

I'm just picking up docker for the first time. The first thing I wanted to learn was best practices for data persistence. Finally, after being misled by dockers own documentation, I realise named volumes are the new standard. I took a lot of energy to learn that. I consider myself lucky I learned it at all. I will continue to learn despite dockers own misleading documentation. I could take some time considering all the second opinions I am now inclined to seek.

@EugenMayer

This comment has been minimized.

Show comment
Hide comment
@EugenMayer

EugenMayer May 10, 2017

@pmatts and most probably your current understanding is already outdated considering what we have now like bind mounts into name volumes using docker create and things like that.

Being active on stack and also providing https://github.com/EugenMayer/docker-sync i regularly deal with users not being able to understand how volume ought to work - especially named volumes are completely missed - it repeats and again and again - e.g. since i just tell people no use a named volume in docker-sync, they stuck on this generally.

So i really find this issue more and more urgent, since the point is, you get far first without understanding named-volumes, so there are (bad) alternatives some might choose first and build upon it. So its not like people will force to find the solution, they will go with the first solution kind works - which makes it even worse later on.

EugenMayer commented May 10, 2017

@pmatts and most probably your current understanding is already outdated considering what we have now like bind mounts into name volumes using docker create and things like that.

Being active on stack and also providing https://github.com/EugenMayer/docker-sync i regularly deal with users not being able to understand how volume ought to work - especially named volumes are completely missed - it repeats and again and again - e.g. since i just tell people no use a named volume in docker-sync, they stuck on this generally.

So i really find this issue more and more urgent, since the point is, you get far first without understanding named-volumes, so there are (bad) alternatives some might choose first and build upon it. So its not like people will force to find the solution, they will go with the first solution kind works - which makes it even worse later on.

@NicolasWebDev

This comment has been minimized.

Show comment
Hide comment
@NicolasWebDev

NicolasWebDev Aug 2, 2017

Is there any news on that front?

Is there an official documentation on named volumes somewhere?

NicolasWebDev commented Aug 2, 2017

Is there any news on that front?

Is there an official documentation on named volumes somewhere?

@cpuguy83

This comment has been minimized.

Show comment
Hide comment
@cpuguy83

cpuguy83 Aug 10, 2017

Contributor

This is now updated https://docs.docker.com/engine/admin/volumes/
Thanks @mstanleyjones!

Contributor

cpuguy83 commented Aug 10, 2017

This is now updated https://docs.docker.com/engine/admin/volumes/
Thanks @mstanleyjones!

@cpuguy83 cpuguy83 closed this Aug 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment