[Bug 1230192] New: Docker fails mounting a volume as readonly on files located under /usr
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1230192
Bug ID: 1230192
Summary: Docker fails mounting a volume as readonly on files
located under /usr
Product: Layered Product Common for RHEL 7
Version: RHEL 7.1
Component: distribution
Assignee: drieden(a)redhat.com
Reporter: dwalsh(a)redhat.com
CC: adimania(a)gmail.com, admiller(a)redhat.com,
bugzilla.redhat.com(a)trancecode.co.uk,
decarr(a)redhat.com, dustymabe(a)redhat.com,
dwalsh(a)redhat.com, extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lhh(a)redhat.com, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, patryk.kubiak(a)gmail.com, s(a)shk.io,
snagar(a)redhat.com, thrcka(a)redhat.com,
vbatts(a)redhat.com, yann.robert(a)anantaplex.fr
Depends On: 1216151
Blocks: 1221688
Group: redhat
+++ This bug was initially created as a clone of Bug #1216151 +++
Description of problem:
Docker fails to run a container with a volume on files located under /usr (or
on symbolic link to files located under /usr) if the ":ro" specification is
used to mount it as readonly
Version-Release number of selected component (if applicable):
docker-io-1.6.0-2.git3eac457.fc21.x86_64
How reproducible: 100%
Steps to Reproduce:
1. install docker package docker-io-1.6.0-2.git3eac457.fc21.x86_64
2. restart the docker service
3. run the following command
docker run -ti -v /etc/localtime:/etc/localtime:ro busybox echo hello
Actual results:
get exit code 1
and message FATA[0000] Error response from daemon: Cannot start container
4bb87515e4eb828b295eb4718a7159c958a1154ed839b29fd213a597b91a200e: [8] System
error: Relabeling content in /usr is not allowed.
Expected results:
get exit code 0
and message "hello"
Additional info:
please refer to initial bug report on docker repository at github
https://github.com/docker/docker/issues/12811
--- Additional comment from colin on 2015-05-12 17:48:40 EDT ---
I see this also on F22
[root@kvm124 ~]# rpm -q docker
docker-1.6.0-3.git9d26a07.fc22.x86_64
This no longer works
docker run -d --sig-proxy --name $CT_name --net=none \
-v /etc/localtime:/etc/localtime:ro \
Editing out the :ro stops the Failure
docker run -d --sig-proxy --name $CT_name --net=none \
-v /etc/localtime:/etc/localtime \
FATA[0000] Error response from daemon: Cannot start container
925387bd2b2988b1a10ff87e68e188f3a579e68d3d5fc1f31d40a648cd9cb6d2: [8] System
error: Relabeling content in /usr is not allowed.
--- Additional comment from Yann Robert on 2015-05-20 05:09:21 EDT ---
Hi, is there any news on this?
docker 1.6.0 on CentOS is working fine with:
# rpm -q docker
docker-1.6.0-11.0.1.el7.centos.x86_64
it still does not work on Fedora with:
$ rpm -q docker-io
docker-io-1.6.0-4.git350a636.fc21.x86_64
--- Additional comment from Derek Carr on 2015-05-26 20:47:55 EDT ---
I am working on moving the Vagrant environment for Kubernetes to Fedora 21.
Kubernetes runs the master services in pods that mount in /usr
To get around this problem, I have to disable selinux on the master server, but
would like to avoid having to do that if possible.
--- Additional comment from Patryk Kubiak on 2015-06-03 06:25:02 EDT ---
It does not work on CentOS 7 OS as well with docker 1.6.0 from EPEL repo:
$ rpm -qi docker
Name : docker
Version : 1.6.0
Release : 11.0.1.el7.centos
Architecture: x86_64
Install Date: Wed 03 Jun 2015 11:15:06 AM CEST
Group : Unspecified
Size : 33835427
License : ASL 2.0
Signature : RSA/SHA256, Thu 14 May 2015 01:50:02 AM CEST, Key ID
24c6a8a7f4a80eb5
Source RPM : docker-1.6.0-11.0.1.el7.centos.src.rpm
Build Date : Thu 14 May 2015 01:47:06 AM CEST
Build Host : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager : CentOS BuildSystem <http://bugs.centos.org>
Vendor : CentOS
URL : http://www.docker.com
Summary : Automates deployment of containerized applications
$ docker run -ti -v /etc/localtime:/etc/localtime:ro busybox echo hello
Unable to find image 'busybox:latest' locally
latest: Pulling from docker.io/busybox
cf2616975b4a: Pull complete
6ce2e90b0bc7: Pull complete
8c2e06607696: Already exists
docker.io/busybox:latest: The image you are pulling has been verified.
Important: image verification is a tech preview feature and should not be
relied on to provide security.
Digest: sha256:38a203e1986cf79639cfb9b2e1d6e773de84002feea2d4eb006b52004ee8502d
Status: Downloaded newer image for docker.io/busybox:latest
Timestamp: 2015-06-03 12:16:19.569470822 +0200 CEST
Code: System error
Message: Relabeling content in /usr is not allowed.
Frames:
---
0: setupRootfs
Package: github.com/docker/libcontainer
File: rootfs_linux.go@34
---
1: Init
Package: github.com/docker/libcontainer.(*linuxStandardInit)
File: standard_init_linux.go@52
---
2: StartInitialization
Package: github.com/docker/libcontainer.(*LinuxFactory)
File: factory_linux.go@223
---
3: initializer
Package: github.com/docker/docker/daemon/execdriver/native
File: init.go@35
---
4: FATA[0004] Error response from daemon: Cannot start container
a9e9dcf572b52fc40a8f6a802fe45e5e461e92a3d9c537cb8c5859e3bff9cc31: [8] System
error: Relabeling content in /usr is not allowed.
It requires to remove ":ro" flag in order to work properly.
--- Additional comment from Daniel Walsh on 2015-06-03 08:14:11 EDT ---
Should be fixed in docker-1.6.2
--- Additional comment from Patryk Kubiak on 2015-06-09 18:02:22 EDT ---
After upgrading to 1.6.2 from virt7-testing repo
(http://wiki.centos.org/Cloud/Docker) problem still seem to exists:
Trying to mount following volume is still not possible:
-v /etc/localtime:/etc/localtime:ro
docker version:
Client version: 1.6.2.el7
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): c3ca5bb/1.6.2
OS/Arch (client): linux/amd64
Server version: 1.6.2.el7
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): c3ca5bb/1.6.2
OS/Arch (server): linux/amd64
Running test container was stopped & removed.
Then docker service was restarted via systemctl.
A new container was started to verify the problem.
Problem still exist with version 1.6.2
--- Additional comment from Daniel Walsh on 2015-06-10 08:20:19 EDT ---
Lokesh I just fixed this issue in docker-1.6.2 repo. Please rebuild for RHEL7
Fedora 21, 22.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1216151
[Bug 1216151] Docker fails mounting a volume as readonly on files located
under /usr
https://bugzilla.redhat.com/show_bug.cgi?id=1221688
[Bug 1221688] Docker fails mounting a volume as readonly on files located
under /usr
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1218639] New: docker push to dockerhub does not work (docker 1.16)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1218639
Bug ID: 1218639
Summary: docker push to dockerhub does not work (docker 1.16)
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Keywords: Extras
Severity: high
Assignee: dwalsh(a)redhat.com
Reporter: miminar(a)redhat.com
QA Contact: lsu(a)redhat.com
CC: adimania(a)gmail.com, admiller(a)redhat.com,
agoldste(a)redhat.com, extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jalmansor(a)gmail.com,
jchaloup(a)redhat.com, jhonce(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
maszulik(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
spousty(a)redhat.com, thrcka(a)redhat.com,
vbatts(a)redhat.com
Depends On: 1217987
Keywords: Extras
+++ This bug was initially created as a clone of Bug #1217987 +++
Description of problem:
I can build and tag a docker image on my local machine but I can not push it to
dockerhub. I am sure I have a dockerhub account and I can push with F20 and
docker 15. Maceij can push with Ubuntu and Docker 16.
Version-Release number of selected component (if applicable):
Docker version 1.6.0, build 3eac457/1.6.0
How reproducible:
Always
Steps to Reproduce:
1. Make a local docker image
2. Tag it
3. Try to push it to dockerhub
Actual results:
$ sudo docker build -t thesteve0/openshift-qpid:latest .
Sending build context to Docker daemon 2.048 kB
Sending build context to Docker daemon
Step 0 : FROM fedora/qpid
---> 6b45d8271e13
Step 1 : MAINTAINER spousty <spousty(a)redhat.com>
---> Using cache
---> 32b450b8f57a
Step 2 : ENV IMAGE_DESCRIPTION QPID C++ AMQP Server 0.30.3
---> Using cache
---> 03be2f186029
Step 3 : ENV IMAGE_TAGS qpid,qpid030,
---> Using cache
---> 13797654c23f
Step 4 : ENV IMAGE_EXPOSE_SERVICES 5672:qpid
---> Using cache
---> 3a0843e1e66e
Step 5 : EXPOSE 5672
---> Using cache
---> 465c93d05637
Step 6 : ENTRYPOINT qpidd -t --auth=no
---> Using cache
---> 4ff0b3679c09
Successfully built 4ff0b3679c09
$ sudo docker images
REPOSITORY TAG IMAGE ID
CREATED VIRTUAL SIZE
thesteve0/openshift-qpid latest 4ff0b3679c09 2
minutes ago 607.1 MB
$ sudo docker push thesteve0/openshift-qpid:latest
Do you really want to push to public registry? [Y/n]: Y
The push refers to a repository [docker.io/thesteve0/openshift-qpid] (len: 1)
FATA[0001] Repository does not exist: docker.io/thesteve0/openshift-qpid
Expected results:
The image should be pushed to dockerhub
Additional info:
--- Additional comment from Steven Citron-Pousty on 2015-05-03 17:11:15 EDT ---
See the thread starting here for this issue hitting another user a few days ago
https://forums.docker.com/t/docker-push-error-fata-0001-respository-does-...
--- Additional comment from Andy Goldstein on 2015-05-03 22:14:23 EDT ---
The current workaround: sudo docker push
docker.io/thesteve0/openshift-qpid:latest. You need to include the docker.io/
prefix when pushing to the Hub.
--- Additional comment from Jason Al-Mansor on 2015-05-04 11:39:52 EDT ---
I've noticed this issue as well. I tried swapping the package binary with the
binary from docker and it worked fine and it didn't display the public registry
prompt.
--- Additional comment from Michal Minar on 2015-05-05 07:24:17 EDT ---
Thank you Steven for reporting this. PR
https://github.com/rhatdan/docker/pull/48 fixes it.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1217987
[Bug 1217987] docker push to dockerhub does not work (docker 1.16)
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
Broken dependencies: docker-io
by Fedora Koji Build System
docker-io has broken dependencies in the epel-6 tree:
On x86_64:
docker-io-devel-1.6.2-1.el6.x86_64 requires /sbin/runscript
Please resolve this as soon as possible.
8 years, 10 months
[Bug 1214619] New: Tracker for golang-github-onsi-ginkgo
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1214619
Bug ID: 1214619
Summary: Tracker for golang-github-onsi-ginkgo
Product: Fedora
Version: rawhide
Component: golang-github-onsi-ginkgo
Assignee: jchaloup(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-onsi-ginkgo for rawhide and other
fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1033606] New: Failed to connect to network from Docker container
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1033606
Bug ID: 1033606
Summary: Failed to connect to network from Docker container
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: mfojtik(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Connecting to external network from Docker container fail due to firewalld. I
guess you must have masquerade enabled, however this is not mentioned anywhere.
I think docker-io should set the firewalld rules automatically, or tell users
that they need to enable masquarade in firewalld.
Version-Release number of selected component (if applicable):
Name : docker-io
Arch : x86_64
Version : 0.7
Release : 0.17.rc6.fc20
Steps to Reproduce:
1. $ yum install docker-io
2. $ systemctl enable docker.service
3. $ systemctl start docker.service
4. $ docker pull mattdm/fedora
5. $ docker run -i -t mattdm/fedora:latest /bin/bash
6. $ ping google.com
ping: unknown host google.com
When I stop firewalld on host (systemctl stop firewalld) and then restart the
docker (systemctl restart docker), the ping works like a charm.
Actual results:
Unable to connect outside the Docker container with firewalld enabled.
Expected results:
Docker should configure firewalld automatically (during install?), or inform
users to do so manually.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
Broken dependencies: docker-io
by Fedora Koji Build System
docker-io has broken dependencies in the epel-6 tree:
On x86_64:
docker-io-devel-1.6.2-1.el6.x86_64 requires /sbin/runscript
Please resolve this as soon as possible.
8 years, 10 months
[Bug 1230453] New: cadvisor-0.15.1 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1230453
Bug ID: 1230453
Summary: cadvisor-0.15.1 is available
Product: Fedora
Version: rawhide
Component: cadvisor
Keywords: FutureFeature, Triaged
Assignee: jchaloup(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Latest upstream release: 0.15.1
Current version/release in rawhide: 0.14.0-1.fc23
URL: https://github.com/google/cadvisor
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
Broken dependencies: docker-io
by Fedora Koji Build System
docker-io has broken dependencies in the epel-6 tree:
On x86_64:
docker-io-devel-1.6.0-1.el6.x86_64 requires /sbin/runscript
Please resolve this as soon as possible.
8 years, 10 months
