Skip to content

Improve documentation for builder.rst / VOLUME command#2632

Closed
codevin wants to merge 1 commit intomoby:masterfrom
codevin:patch-1
Closed

Improve documentation for builder.rst / VOLUME command#2632
codevin wants to merge 1 commit intomoby:masterfrom
codevin:patch-1

Conversation

@codevin
Copy link
Contributor

@codevin codevin commented Nov 10, 2013

Updated builder.rst to make VOLUME command documentation more precise and avoid confusion.

Updated builder.rst to make VOLUME command documentation more precise and avoid confusion.
@vieux
Copy link
Contributor

vieux commented Nov 12, 2013

/cc @metalivedev

@ghost ghost assigned metalivedev Nov 13, 2013
@metalivedev
Copy link
Contributor

Howdy -- thank you for this improvement, but there are some problems:

  1. The indentation is wrong, so it doesn't look right when Sphinx parses it.
  2. This is repetition of information from the working with volumes document. I don't like to repeat information -- links are better.

I agree that if you're looking at the VOLUMES documentation then you are interested in more information, so I think the right thing to do here is replace all of your text with something like this:

For more information about how to use ``VOLUMES`` please see the :ref:`volume_def` documentation. That includes examples of how to use volumes both in a Dockerfile and at runtime.

Could you update your pull request?

/Andy

@codevin
Copy link
Contributor Author

codevin commented Nov 13, 2013

How about this line? Essentially bringing out the behaviour explicitly in one line. Also note that I am using the term "mount point", which seems appropriate.

The ``VOLUME`` instruction will create a mount point with the specified name and mark it as holding externally mounted volumes from native host or other containers.  For more information/examples and mounting instructions via docker client, see the :ref:`volume_def` documentation. 

Is this OK?

@metalivedev
Copy link
Contributor

Your sentence sounds fine. Thanks!

@metalivedev
Copy link
Contributor

fixed in #2690

thaJeztah added a commit to thaJeztah/docker that referenced this pull request May 25, 2021
…91130ec8

Update libnetwork to make `docker run -p 80:80` functional again on environments
with kernel boot parameter `ipv6.disable=1`.

full diff: moby/libnetwork@b350742...64b7a45

- fix port forwarding with ipv6.disable=1
    - fixes moby/moby/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
    - fixes docker/libnetwork/2629 Network issue with IPv6 following update to version 20.10.6
    - fixesdocker/for-linux/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
- Enforce order of lock acquisitions on network/controller, fixes moby#2632
    - fixes docker/libnetwork/2632 Name resolution stuck due to deadlock between different network struct methods
    - fixes moby/moby/42032 Docker deamon get's stuck, can't serve DNS requests

Signed-off-by: Sebastiaan van Stijn <[email protected]>
thaJeztah added a commit to thaJeztah/docker that referenced this pull request May 25, 2021
…91130ec8

Update libnetwork to make `docker run -p 80:80` functional again on environments
with kernel boot parameter `ipv6.disable=1`.

full diff: moby/libnetwork@b350742...64b7a45

- fix port forwarding with ipv6.disable=1
    - fixes moby/moby/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
    - fixes docker/libnetwork/2629 Network issue with IPv6 following update to version 20.10.6
    - fixesdocker/for-linux/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
- Enforce order of lock acquisitions on network/controller, fixes moby#2632
    - fixes docker/libnetwork/2632 Name resolution stuck due to deadlock between different network struct methods
    - fixes moby/moby/42032 Docker deamon get's stuck, can't serve DNS requests

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit e4109b3)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
cpuguy83 pushed a commit to cpuguy83/docker that referenced this pull request May 25, 2021
cpuguy83 pushed a commit to cpuguy83/docker that referenced this pull request May 25, 2021
Enforce order of lock acquisitions on network/controller, fixes moby#2632
nosamad pushed a commit to WAGO/docker-engine that referenced this pull request Sep 13, 2021
…91130ec8

Update libnetwork to make `docker run -p 80:80` functional again on environments
with kernel boot parameter `ipv6.disable=1`.

full diff: moby/libnetwork@b350742...64b7a45

- fix port forwarding with ipv6.disable=1
    - fixes moby/moby/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
    - fixes docker/libnetwork/2629 Network issue with IPv6 following update to version 20.10.6
    - fixesdocker/for-linux/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
- Enforce order of lock acquisitions on network/controller, fixes moby#2632
    - fixes docker/libnetwork/2632 Name resolution stuck due to deadlock between different network struct methods
    - fixes moby/moby/42032 Docker deamon get's stuck, can't serve DNS requests

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit e4109b3)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
nosamad pushed a commit to WAGO/docker-engine that referenced this pull request Sep 15, 2021
…91130ec8

Update libnetwork to make `docker run -p 80:80` functional again on environments
with kernel boot parameter `ipv6.disable=1`.

full diff: moby/libnetwork@b350742...64b7a45

- fix port forwarding with ipv6.disable=1
    - fixes moby/moby/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
    - fixes docker/libnetwork/2629 Network issue with IPv6 following update to version 20.10.6
    - fixesdocker/for-linux/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
- Enforce order of lock acquisitions on network/controller, fixes moby#2632
    - fixes docker/libnetwork/2632 Name resolution stuck due to deadlock between different network struct methods
    - fixes moby/moby/42032 Docker deamon get's stuck, can't serve DNS requests

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit e4109b3)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
nosamad pushed a commit to WAGO/docker-engine that referenced this pull request Sep 28, 2021
…91130ec8

Update libnetwork to make `docker run -p 80:80` functional again on environments
with kernel boot parameter `ipv6.disable=1`.

full diff: moby/libnetwork@b350742...64b7a45

- fix port forwarding with ipv6.disable=1
    - fixes moby/moby/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
    - fixes docker/libnetwork/2629 Network issue with IPv6 following update to version 20.10.6
    - fixesdocker/for-linux/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
- Enforce order of lock acquisitions on network/controller, fixes moby#2632
    - fixes docker/libnetwork/2632 Name resolution stuck due to deadlock between different network struct methods
    - fixes moby/moby/42032 Docker deamon get's stuck, can't serve DNS requests

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit e4109b3)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants