There is an open bug in tmpfs that results in permissions being reset on container restart. At this point it has tripped up quite a few people. This adds a hint about the issue, and a link to a the workaround we ultimately used (a functionality not mentioned elsewhere in the docs).
* Update "Mounts" example
In the original example, the "Mounts" field returned by `docker container inspect [CONTAINER]` was not shown. This may be too much data, but we should at least show the "Mounts" field so folks know what to look for.
* shortened the docker inspect example
Co-authored-by: David Karlsson <david.karlsson@docker.com>
Mount propagation is not supported for named volumes, as mentioned in
the paragraph before this one, so let's remove it here.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The current wording implies that ANY bind mount into a non-empty directory will obscure the files in that directory, but while that's true of bind mounting a directory, it's not true if bind-mounting a single file (from my testing, in a linux container running Docker Desktop for Windows).
I simply added that minor (but important) clarification of "a directory".
These were notes about distro versions that have been EOL for a long
time, and an old version of docker engine that's EOL as well.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Add information on compose usage.
Add information on how to declare a bind mount in docke compose.
* Apply suggestions from code review
* Update storage/bind-mounts.md
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
There is an error in the example commands of Step 9 in the copy on write strategy section of the [About storage drivers](https://docs.docker.com/storage/storagedriver/#the-copy-on-write-cow-strategy) page. The first command should reference the `acme/my-base-image:1.0` image and the second command should reference the `acme/my-final-image:1.0`.
* Change section headers for backing up/restoring volumes to use "volume" instead of "container"
The section headers "Backup a container" and "Restore container from backup" are used as headers for sections that are actually about backing up and restoring volumes.
* Minor style update
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
* Add anonymous volumes autoremove info
Anonymous volumes aren't removed if another container adopts them with `--volumes-from`, see: https://github.com/docker/docker.github.io/issues/13435
* Format Note
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
* Minor `read-only` clarification
## Why
It was not obvious to me that `ro` is the shorthand form of `readonly`.
## Description
This adds a bit of text to explicitly state that `ro` is the shorthand form of `readonly` when using volumes
* Update storage/volumes.md
Co-authored-by: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
Co-authored-by: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Fix broken link to Windows path troubleshooting
* Update the cross-reference
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
* Document path conversion on Windows
* Minor formatting and style updates
* desktop/windows: minor fixes in troubleshoot
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>