Bug 1323819 - docker volumes are blocked even when there is a bind mount over it with --no-volumes
Summary: docker volumes are blocked even when there is a bind mount over it with --no-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 19:45 UTC by Mrunal Patel
Modified: 2019-03-06 00:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 16:18:08 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1274 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2016-06-23 20:12:28 UTC

Description Mrunal Patel 2016-04-04 19:45:01 UTC
Description of problem:

Create a simple docker image with a VOLUME

FROM busybox
VOLUME ["/var/www"]
CMD ["echo", 'abcd"]

Set the docker daemon config for --no-volumes in /etc/sysconfig/docker:
OPTIONS='--selinux-enabled --log-driver=journald --no-volumes=true'

docker run fails to start when we try to bind mount a volume over the VOLUME:
$ docker run -v ~/tempdir:/var/www <image-name>
It fails with the error that volumes are not allowed when they should in this case.

Version-Release number of selected component (if applicable):
1.9.1

Comment 2 Lokesh Mandvekar 2016-04-04 20:24:24 UTC
fixed by https://github.com/projectatomic/docker/pull/92

Comment 3 Daniel Walsh 2016-06-03 13:02:52 UTC
Fixed in docker-1.10

Comment 5 Luwen Su 2016-06-11 17:36:48 UTC
In docker-1.10.3-40.el7.x86_64
# docker run -v ~/tempdir:/var/www 6e5aceba76ed
abcd

Comment 7 errata-xmlrpc 2016-06-23 16:18:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1274


Note You need to log in before you can comment on or make changes to this bug.