Collected issues with Volumes #6496
Description
- Base Images & Volume & mkdir #3639 - Volumes don’t work for base images
- Add ability to mount volume as user other than root #2259 - Setting permissions on bind mounted volumes
- VOLUME(S)-FROM in dockerfiles; equivalent of docker run's -volumes-from #3949 Fix for two identical broken blog-post links. #5229 - Build-only data
- docker cp should support VOLUMEs #1992 -
docker cpdoesn’t work with volumes - Recursive bind mounting #3782 - recursive bind mounting (--rbind instead of —bind)
- possible to rm a container that is being used by other containers via -volumes-from #3634 Inconsistency of volume deletion between 'docker run -rm' and 'docker rm' #4356 - volume garbage collection (last comment) # can be handled with named volumes and external volume drivers
- docker volumes w remote daemon #4023 - Mount remote volumes (client is remote, path is local to client)
- Changeable/Editable volumes / ports #2045 - dynamically change volumes
- container removed, where were those volumes? #6504 - Volume recovery (after corrosponding container removed) # named volumes resolves this
- [POC] idea for docker data volume containers backup/restoration #6556 - Backup/restore volumes
- Volumes pretty much always need a data-container #6698 - Volumes need data-containers to be useful - # hanlded by named volumes and external volume drivers
- option to mount volumes noexec #7054 - Expand perm handling of volumes