May 2015 - golang - Fedora mailing-lists

[Bug 1210364] New: Embedded kubelet cadvisor fails to enumerate docker containers
by Red Hat Bugzilla 29 Jun '16

29 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1210364 Bug ID: 1210364 Summary: Embedded kubelet cadvisor fails to enumerate docker containers Product: Fedora Version: 22 Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: stefw(a)redhat.com 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, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: The cAdvisor embedded in kubelet fails to enumerate docker containers. It fails with the message: failed to get all Docker containers with error: unable to find data for container /system.slice/docker-....scope Version-Release number of selected component (if applicable): kubernetes-0.13.2-0.5.git8d94c43.fc22.x86_64 How reproducible: Every time. Tried restarting Docker. Steps to Reproduce: 1. http://localhost:4194/api/v1.2/docker 1. Or just go to http://localhost:4194 and click on 'Docker Containers' to see the same thing. Actual results: failed to get all Docker containers with error: unable to find data for container /system.slice/docker-9dade0a01bf0368b6c0dad722f7e85af98593dde00873e6abb2cfd86d2d2b7a9.scope Expected results: Output like this: {"/system.slice/docker-1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1.scope":{"name":"/system.slice/docker-1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1.scope","aliases":["k8s_ruby-helloworld.8ec853e6_frontend-58wav_default_19192267-d9c8-11e4-b2d6-10c37bdb8410_025ed744","1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1"],"namespace":"docker","spec":{"creation_time":"0001-01-01T00:00:00Z","has_c... Additional info: When running standalone cadvisor I get the above expected output. cadvisor-0.10.1-0.1.gitef7dddf.fc22.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1223445] New: Update flannel to the latest commit to get "mutli-network support and abstract subnet mgr"
by Red Hat Bugzilla 23 Jun '16

23 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1223445 Bug ID: 1223445 Summary: Update flannel to the latest commit to get "mutli-network support and abstract subnet mgr" Product: Fedora Version: rawhide Component: flannel Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, linville(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Update to at least [1] [1] https://github.com/coreos/flannel/commit/9cbad3b7f08e8e2a803d00dbbeeba3a444… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1038683] New: golang appears to contain an ECC implementation
by Red Hat Bugzilla 17 Jun '16

17 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1038683 Bug ID: 1038683 Summary: golang appears to contain an ECC implementation Product: Fedora Version: 20 Component: golang Assignee: adam(a)spicenitz.org Reporter: notting(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, skottler(a)redhat.com, vbatts(a)redhat.com Blocks: 182235 (FE-Legal), 1019390 (ecc) Description of problem: At least, I would assume that's what is in go/src/pkg/crypto/elliptic/. In Fedora, we only ship certain reviewed curves. Version-Release number of selected component (if applicable): 1.2-1 How reproducible: 100% Steps to Reproduce: 1. look at golang's crypto code Actual results: Hey, that looks like ECC, and it appears to have been always included. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=182235 [Bug 182235] Fedora Legal Tracker https://bugzilla.redhat.com/show_bug.cgi?id=1019390 [Bug 1019390] [tracking bug] re-enable ECC/ECDHE/EC/ECDSA/elliptic curves in Fedora -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1046469] New: docker privileged mode with cmd /sbin/init - agetty & high cpu
by Red Hat Bugzilla 08 Jun '16

08 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1046469 Bug ID: 1046469 Summary: docker privileged mode with cmd /sbin/init - agetty & high cpu Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: fortuik(a)gmail.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, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: docker containers in privileged mode mess with the host agetty and produce very hicht cpu load Version-Release number of selected component (if applicable): Fedora 20 Docker 0.7.1, 0.7.2 How reproducible: docker run -privileged -d mattdm/fedora:latest /sbin/init Actual results: docker container runs cpu load is very high - agetty stopping the container & the docker daemon do not free the cpu resources one have to kill the agetty process Expected results: docker container runs Additional info: In my real case i run rhel containers with puppet & ssh daemons for a small puppet lab. The reason i met this bug is that running docker container with /sbin/init cmd under RHEL 6.5 require priviliged mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1192081] New: Modify base image Dockerfile to enable systemd to run smoothly
by Red Hat Bugzilla 08 Jun '16

08 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1192081 Bug ID: 1192081 Summary: Modify base image Dockerfile to enable systemd to run smoothly Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vpavlin(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: systemd requires container=docker set in env and /run, /tmp to be mountpoints start successfully. In my opinion, we should add ENV container=docker VOLUME ['/run', '/tmp'] to the base image Dockerfile. Command docker run --it --rm -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora:rawhide /usr/sbin/init would then be all an user would need to "boot" systemd in a container. I've already made some changes in KS file - remove fstab and machine-id, mask mount units... which make the boot sequence smooth. More changes to boot sequence will probably come later (f.e. switch from graphical.target to multi-user target) I'd also like to suggest new Rawhide build to be pushed to registry. This one works for me quite well: http://koji.fedoraproject.org/koji/taskinfo?taskID=8883309 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1192848] New: docker no longer supports socket-activation
by Red Hat Bugzilla 03 Jun '16

03 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1192848 Bug ID: 1192848 Summary: docker no longer supports socket-activation Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: tim(a)gfxmonk.net QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Version-Release number of selected component (if applicable): docker-io-1.4.1-8.fc21.x86_64 How reproducible: Always Steps to Reproduce: $ docker ps Actual results: FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host? Expected results: /var/run/docker.sock should automatically start `docker.service` via socket activation. This was the case on fedora 20. Additional info: I looked in the package history, and it looks like it was disabled by: commit aecb9bfe55824e2c9c7be4afce3ac8dd7e3395f5 Author: Lokesh Mandvekar <lsm5(a)fedoraproject.org> Date: Fri Jan 16 17:06:40 2015 +0000 docker group and socket activation not used NVR: docker-io-1.4.1-7 - sysconfig file updates Signed-off-by: Lokesh Mandvekar <lsm5(a)fedoraproject.org> I assume there's a reason for this, but there's no bugzilla or other issue reference, and no description of why the functionality should be removed. The removal of socket activation is pretty annoying, so it would be great if it could be re-enabled. If it can't be enabled, it would be good to document why. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1214778] New: Tracker for golang-github-prometheus-procfs
by Red Hat Bugzilla 31 May '16

31 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214778 Bug ID: 1214778 Summary: Tracker for golang-github-prometheus-procfs Product: Fedora Version: rawhide Component: golang-github-prometheus-procfs 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-prometheus-procfs 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.

1 39

[Bug 1220164] New: Tracker for golang-github-syndtr-gosnappy
by Red Hat Bugzilla 31 May '16

31 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1220164 Bug ID: 1220164 Summary: Tracker for golang-github-syndtr-gosnappy Product: Fedora Version: rawhide Component: golang-github-syndtr-gosnappy Severity: low Priority: low 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-syndtr-gosnappy 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.

1 30

[Bug 1222336] New: Tracker for golang-github-shurcooL-sanitized_anchor_name
by Red Hat Bugzilla 31 May '16

31 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1222336 Bug ID: 1222336 Summary: Tracker for golang-github-shurcooL-sanitized_anchor_name Product: Fedora Version: rawhide Component: golang-github-shurcooL-sanitized_anchor_name Severity: low Priority: low 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, jcajka(a)redhat.com, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-shurcooL-sanitized_anchor_name 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.

1 46

[Bug 1091538] New: golang crashing on ARMv7
by Red Hat Bugzilla 09 May '16

09 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1091538 Bug ID: 1091538 Summary: golang crashing on ARMv7 Product: Fedora Version: rawhide Component: golang Assignee: adam(a)spicenitz.org Reporter: pbrobinson(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Blocks: 245418 (ARMTracker) We're getting an crash with go when I try and enable go support for ARM in the swig package. http://koji.fedoraproject.org/koji/taskinfo?taskID=6780663 It's currently just a scratch build as I obviously can't push it if it fails. checking Examples/go/callback checking Examples/go/class unexpected fault address 0x40440000 fatal error: fault [signal 0xb code=0x1 addr=0x40440000 pc=0x40440000] goroutine 1 [running]: runtime.throw(0x15691f) /usr/lib/golang/src/pkg/runtime/panic.c:464 +0x5c fp=0xb6ba5f7c runtime: unexpected return pc for runtime.sigpanic called from 0x40440000 runtime.sigpanic() /usr/lib/golang/src/pkg/runtime/os_linux.c:237 +0xa8 fp=0xb6ba5f88 goroutine 3 [syscall]: runtime.goexit() /usr/lib/golang/src/pkg/runtime/proc.c:1394 checking Examples/go/constants make[3]: *** [go_run] Error 2 make[2]: *** [check] Error 2 make[1]: *** [class.actionexample] Error 2 checking Examples/go/enum checking Examples/go/extend checking Examples/go/funcptr checking Examples/go/multimap checking Examples/go/pointer checking Examples/go/reference checking Examples/go/simple checking Examples/go/template checking Examples/go/variables Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=245418 [Bug 245418] Tracker for ARM support -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1211266] New: Tracking bugzilla for kubernetes updates
by Red Hat Bugzilla 07 May '16

07 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1211266 Bug ID: 1211266 Summary: Tracking bugzilla for kubernetes updates Product: Fedora Version: rawhide Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com 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, nhorman(a)redhat.com, vbatts(a)redhat.com Tracker used for kubernetes updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 86

[Bug 1200612] New: Package rocksdb binary for Fedora
by Red Hat Bugzilla 03 May '16

03 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1200612 Bug ID: 1200612 Summary: Package rocksdb binary for Fedora Product: Fedora Version: rawhide Component: golang-github-influxdb-rocksdb Assignee: jchaloup(a)redhat.com Reporter: ggillies(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com Hi, With influxdb version 0.9 moving to completely utilise rocksdb, we probably want to look at expanding this package to fully provide a rocksdb compiled binary. That is, a rocksdb package that has /usr/bin/rocksdb, as well as the devel package with the raw go code for deps (which this package currently provides) Regards, Graeme -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1100000] New: can't run iscsid in a docker container
by Red Hat Bugzilla 11 Apr '16

11 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1100000 Bug ID: 1100000 Summary: can't run iscsid in a docker container Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jslagle(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 898086 --> https://bugzilla.redhat.com/attachment.cgi?id=898086&action=edit iscsid strace showing failure Description of problem: Can't start iscsid in a docker container Version-Release number of selected component (if applicable): # rpm -q docker-io docker-io-0.11.1-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. use the published fedora image, docker pull fedora 2. start the container, docker run -t -i fedora /bin/bash 3. install iscsi-initiator-utils 4. try to start iscsid: bash-4.2# iscsid -f iscsid: can not bind NETLINK_ISCSI socket strace also attached -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1222338] New: Tracker for golang-github-shurcooL-sanitized_anchor_name
by Red Hat Bugzilla 08 Apr '16

08 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1222338 Bug ID: 1222338 Summary: Tracker for golang-github-shurcooL-sanitized_anchor_name Product: Fedora Version: rawhide Component: golang-github-russross-blackfriday Severity: low Priority: low Assignee: lsm5(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, jcajka(a)redhat.com, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-russross-blackfriday 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.

1 39

[Bug 1096273] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla 05 Apr '16

05 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096273 Bug ID: 1096273 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Severity: low Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1087704 +++ This bug was initially created as a clone of Bug #1087704 +++ Description of problem: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... --- Additional comment from Lukas Doktor on 2014-05-05 03:59:30 EDT --- I retested this with the upstream dc9c28f/0.10.0 with the same results. The daemon output is: ... [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) ... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087704 [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1202517] New: docker fd leak
by Red Hat Bugzilla 02 Apr '16

02 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1202517 Bug ID: 1202517 Summary: docker fd leak Product: Red Hat Enterprise Linux 7 Version: 7.2 Component: docker Assignee: dwalsh(a)redhat.com Reporter: dwalsh(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: adimania(a)gmail.com, admiller(a)redhat.com, arozansk(a)redhat.com, b(a)wtnb.mydns.jp, dwalsh(a)redhat.com, extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jeder(a)redhat.com, jmario(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, srao(a)redhat.com, thrcka(a)redhat.com, tstclair(a)redhat.com, vbatts(a)redhat.com, vgoyal(a)redhat.com Depends On: 1189028 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1189028 [Bug 1189028] docker fd leak -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1189028] New: docker 1.4.1-3.el6 fd leak
by Red Hat Bugzilla 02 Apr '16

02 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1189028 Bug ID: 1189028 Summary: docker 1.4.1-3.el6 fd leak Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: b(a)wtnb.mydns.jp QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: docker daemon doesn't close file descriptor. Version-Release number of selected component (if applicable): docker-io-1.4.1-3.el6.x86_64 How reproducible: Steps to Reproduce: 1. while true; do docker run -t -i --rm busybox /bin/true ; done 2. (in other terminal) DEBUG=1 docker info 3. check values at Fds: and Goroutines: lines Actual results: Fds and Goroutines values are increased forever Expected results: Additional info: - It doesn't happen on RHEL7 + docker 1.4.1 - It doesn't happen on RHEL6 + docker-io-1.3.2-2.el6.x86_64 # lsof -p $(pidof docker) <snip> docker 7771 root 14u REG 0,9 0 3791 [eventfd] docker 7771 root 15u REG 0,9 0 3791 [eventfd] docker 7771 root 16r REG 0,21 0 20709 /cgroup/memory/docker/98b529e398bec4568c58ea96088aef1535eca504bed6453bab8f6f7803d31cfb/memory.oom_control (deleted) docker 7771 root 17u REG 0,9 0 3791 [eventfd] docker 7771 root 18r REG 0,21 0 21176 /cgroup/memory/docker/bc213d3e80815021780064874665fe80801c5a1010d1c0bc4bd5b118ca45d11f/memory.oom_control (deleted) docker 7771 root 19u REG 0,9 0 3791 [eventfd] docker 7771 root 20r REG 0,21 0 21626 /cgroup/memory/docker/7b8d59ec4f23c14e2732726594460ccf89fe31c06e60fabbdc4e358f794af102/memory.oom_control (deleted) docker 7771 root 21w REG 0,9 0 3791 [eventfd] docker 7771 root 22r REG 0,21 0 22112 /cgroup/memory/docker/99ac44fcb18a3e1aea00a5e7cfb040942f2c4f2c673c291105c367788e49d0f2/memory.oom_control (deleted) docker 7771 root 24r REG 0,21 0 22672 /cgroup/memory/docker/b1804ae48289df81d3a5c54167baf729612e12c552ef98917df90d8645d235ad/memory.oom_control (deleted) <snip> # ps $(pidof docker) m PID TTY STAT TIME COMMAND 7771 pts/0 - 0:09 /usr/bin/docker -d - - Sl 0:02 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:01 - - - Sl 0:00 - <snip> -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1214958] New: etcd-v2.1.0-alpha.0 is available
by Red Hat Bugzilla 01 Apr '16

01 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214958 Bug ID: 1214958 Summary: etcd-v2.1.0-alpha.0 is available Product: Fedora Version: rawhide Component: etcd Keywords: FutureFeature, Triaged Assignee: lacypret(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: avagarwa(a)redhat.com, eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lacypret(a)gmail.com, lemenkov(a)gmail.com, lsm5(a)redhat.com, walters(a)redhat.com Latest upstream release: v2.1.0-alpha.0 Current version/release in rawhide: 2.0.10-1.fc23 URL: https://github.com/coreos/etcd 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.

1 21

[Bug 1214769] New: Tracker for golang-github-spf13-cobra
by Red Hat Bugzilla 17 Mar '16

17 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214769 Bug ID: 1214769 Summary: Tracker for golang-github-spf13-cobra Product: Fedora Version: rawhide Component: golang-github-spf13-cobra 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-spf13-cobra 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.

1 36

[Bug 1214797] New: Tracker for golang-github-matttproud-golang_protobuf_extensions
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214797 Bug ID: 1214797 Summary: Tracker for golang-github-matttproud-golang_protobuf_extensions Product: Fedora Version: rawhide Component: golang-github-matttproud-golang_protobuf_extensions 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-matttproud-golang_protobuf_extensions 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.

1 14

[Bug 1214731] New: Tracker for golang-github-spf13-pflag
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214731 Bug ID: 1214731 Summary: Tracker for golang-github-spf13-pflag Product: Fedora Version: rawhide Component: golang-github-spf13-pflag Assignee: lsm5(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-spf13-pflag 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.

1 34

[Bug 1214784] New: Tracker for golang-github-prometheus-client_golang
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214784 Bug ID: 1214784 Summary: Tracker for golang-github-prometheus-client_golang Product: Fedora Version: rawhide Component: golang-github-prometheus-client_golang 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-prometheus-client_golang 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.

1 36

[Bug 1222796] New: Tracker for golang-github-cpuguy83-go-md2man
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1222796 Bug ID: 1222796 Summary: Tracker for golang-github-cpuguy83-go-md2man Product: Fedora Version: rawhide Component: golang-github-cpuguy83-go-md2man Severity: low Priority: low Assignee: lsm5(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, jcajka(a)redhat.com, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-cpuguy83-go-md2man 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.

1 19

[Bug 1215656] New: Tracker for golang-github-fsouza-go-dockerclient
by Red Hat Bugzilla 21 Feb '16

21 Feb '16

https://bugzilla.redhat.com/show_bug.cgi?id=1215656 Bug ID: 1215656 Summary: Tracker for golang-github-fsouza-go-dockerclient Product: Fedora Version: rawhide Component: golang-github-fsouza-go-dockerclient Assignee: lsm5(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, eparis(a)redhat.com, 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-fsouza-go-dockerclient 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.

1 48

[Bug 1204620] New: container stays around wihtout any processes in it
by Red Hat Bugzilla 17 Feb '16

17 Feb '16

https://bugzilla.redhat.com/show_bug.cgi?id=1204620 Bug ID: 1204620 Summary: container stays around wihtout any processes in it Product: Fedora Version: 22 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mvollmer(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Created attachment 1005245 --> https://bugzilla.redhat.com/attachment.cgi?id=1005245&action=edit Setup script for reproducing Description of problem: When running a specific custom image (see attachement), docker fails to notice when the single process exits. The container stays around, and attempts to stop or remove it result in errors. Doing the same with a slightly older version of docker shows expected behavior. Version-Release number of selected component (if applicable): docker-io-1.5.0-19.git5d7adce.fc22.x86_64 How reproducible: Always. Steps to Reproduce: 1. Run the attached SETUP script in an empty directory 2. Run the resulting image # docker run --name=probe cp /bin/container-probe 3. After wrestling control back from the hanging "docker run", try to stop or remove the container. # docker stop probe # docker rm -f probe Actual results: The expected output of container-probe is shown, but "docker run ..." does not return to the command line prompt. In fact, job control doesn't work anymore either (C-c, C-z, C-\). Stopping and removing leads to these errors: # docker stop probe Error response from daemon: Cannot stop container probe: active container for c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist FATA[0000] Error: failed to stop one or more containers # docker rm -f probe Error response from daemon: Could not kill running container, cannot remove - active container for c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist FATA[0000] Error: failed to remove one or more containers Expected results: The output is shown and "docker run" terminates successfully, the container is show as "exited" and can be removed. Additional info: docker-io-1.5.0-1.fc21.x86_64 shows the expected behavior. "docker run -i" return control to the shell, but the resulting container can't be stopped or removed either. "systemctl restart docker" puts the "probe" container into a state where it can be removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1145659] New: [PATCH] Support /etc/sysconfig/docker-storage
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1145659 Bug ID: 1145659 Summary: [PATCH] Support /etc/sysconfig/docker-storage Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)fedoraproject.org Reporter: walters(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, dwalsh(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com, virt-bugs(a)redhat.com Depends On: 1144206 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1144206 [Bug 1144206] [PATCH] Support /etc/sysconfig/docker-storage -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1096296] New: man page inaccuracy about --sig-proxy and --tty
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096296 Bug ID: 1096296 Summary: man page inaccuracy about --sig-proxy and --tty Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com, whenry(a)redhat.com Depends On: 1087697 +++ This bug was initially created as a clone of Bug #1087697 +++ Description of problem: Hi guys, the man page states: --sig-proxy=true: Proxify all received signal to the process (even in non-tty mode) But the real behavior is, that sig-proxy doesn't work when --tty=true. It should be mentioned in there, taht --sig-proxy is incompatible with --tty. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. man docker Actual results: man page says it works even in non-tty Expected results: man page warns that --tty can't be used with --sig-proxy How to verify: 1. docker run --tty=true -i --rm fedora bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps -ax | grep docker 3. kill -SIGUSR1 $PID 4. (with --tty=true no signals are received, when you try the same with --tty=false, signals are proxified and messages are displayed) --- Additional comment from Lokesh Mandvekar on 2014-04-15 02:11:48 EDT --- Copying William (he recently got per subcommand manpages merged upstream). this seems to be the case even in the latest manpage (I'm guessing this was inherited from the original manpage). William, was there any discussion about this in your PR? --- Additional comment from Lokesh Mandvekar on 2014-04-15 02:15:31 EDT --- btw, the 0.10 rpm includes the latest manpages (should be in yum soon) --- Additional comment from Lukas Doktor on 2014-04-15 04:45:55 EDT --- Thanks for a quick reply. I tried the docker-io-0.10.0-2.fc20.x86_64 which says: --sig-proxy=true|false: When set to true, proxify all received signals to the process (even in non-tty mode). The default is true. I'd really like to change it to "only in non-tty" with possible warning that --tty=true is incompatible with --sig-proxy. --- Additional comment from William Henry on 2014-04-30 15:54:25 EDT --- I go this text from upstream. I'll check. --- Additional comment from William Henry on 2014-04-30 16:02:22 EDT --- Lukas,according to the folks upstream, this is a bug in docker run and attach. It should be as the text suggests. Can you file a bug upstream with docker? Here: https://github.com/dotcloud/docker/issues Please just take the information you posted above and post it there. Thanks. Well spotted. Best, William --- Additional comment from Lukas Doktor on 2014-05-02 04:02:01 EDT --- Upstream tracer: https://github.com/dotcloud/docker/issues/5547 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087697 [Bug 1087697] man page inaccuracy about --sig-proxy and --tty -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1096276] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096276 Bug ID: 1096276 Summary: signal 27 (SIGPROF) not passed to container using --sig-proxy Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1087720 +++ This bug was initially created as a clone of Bug #1087720 +++ Description of problem: When I send signal 27 to the docker process, which is running with --sig-proxy=true, it's not forwarded. Other signals are... Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.1-1.fc21.x86_64 upstream Docker version 0.10.0, build dc9c28f/0.10.0 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -27 $PID Actual results: nothing Expected results: Received 27, ignoring... Additional info: When you send any other signal (apart from 19 or 9) it works fine. --- Additional comment from Lukas Doktor on 2014-04-15 04:59:24 EDT --- The signal 17 is also ignored. --- Additional comment from Lukas Doktor on 2014-05-05 03:48:25 EDT --- The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087720 [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1217613] New: Cannot start container [8] System error: mountpoint for cpuset not found
by Red Hat Bugzilla 02 Dec '15

02 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1217613 Bug ID: 1217613 Summary: Cannot start container [8] System error: mountpoint for cpuset not found Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: jiri.folta(a)centrum.cz QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Created attachment 1020711 --> https://bugzilla.redhat.com/attachment.cgi?id=1020711&action=edit screenshot of the error Description of problem: when trying to run a container using Cockpit I get "System error: mountpoint for cpuset not found" error Version-Release number of selected component (if applicable): cockpit: Version 0.27. Built on Wed Mar 25 12:53:20 UTC 2015. How reproducible: allways Steps to Reproduce: 1.Install minimal Fedora 21 for arm platform from http://www.digitaldreamtime.co.uk/images/Fidora/21/ 2.update the system 3.install cockpit and docker 4.login to the server using web interface https://ip:9090 5.download Image: docker.io/wordpress:latest 6. try running the image Actual results: you get an error message(attached) Expected results: actually running the image Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1212190] New: Unable to 'docker login' with 1.6.0-0.1.rc6.fc21
by Red Hat Bugzilla 02 Dec '15

02 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1212190 Bug ID: 1212190 Summary: Unable to 'docker login' with 1.6.0-0.1.rc6.fc21 Product: Fedora Version: 21 Component: docker-io Keywords: Extras Assignee: ichavero(a)redhat.com Reporter: agoldste(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, dwalsh(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, lsu(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Depends On: 1212188 The same issue reported below exists in 1.6.0-0.1.rc6.fc21 +++ This bug was initially created as a clone of Bug #1212188 +++ Description of problem: I'm unable to 'docker login' using 1.6.0-2.el7 Version-Release number of selected component (if applicable): docker-1.6.0-2.el7 How reproducible: 100% Steps to Reproduce: 1. docker login -u <user> -p <pass> -e <email> Actual results: FATA[0001] Post http:///var/run/docker.sock/v1.18/auth: EOF. Are you trying to connect to a TLS-enabled daemon without TLS? Expected results: WARNING: login credentials saved in /home/vagrant/.dockercfg. Login Succeeded Additional info: >From journalctl: time="2015-04-15T13:18:12-04:00" level=info msg="POST /v1.18/auth" time="2015-04-15T13:18:12-04:00" level=info msg="+job auth()" time="2015-04-15T13:18:12-04:00" level=info msg="-job auth()" 2015/04/15 13:18:12 http: panic serving @: runtime error: invalid memory address or nil pointer dereference goroutine 2838 [running]: net/http.funcÂ·011() /usr/lib/golang/src/net/http/server.go:1130 +0xbb fp=0xc20810d4c8 sp=0xc20810d3e8 runtime.call16(0xc20810def0, 0xc209c32510, 0x0) /usr/lib/golang/src/runtime/asm_amd64.s:401 +0x45 fp=0xc20810d4e0 sp=0xc20810d4c8 runtime.gopanic(0xb15060, 0xc20802a050) /usr/lib/golang/src/runtime/panic.go:387 +0x3a8 fp=0xc20810d548 sp=0xc20810d4e0 runtime.panicmem() /usr/lib/golang/src/runtime/panic.go:42 +0x4e fp=0xc20810d570 sp=0xc20810d548 runtime.sigpanic() /usr/lib/golang/src/runtime/sigpanic_unix.go:26 +0x274 fp=0xc20810d5c0 sp=0xc20810d570 github.com/docker/docker/registry.NewEndpoint(0x0, 0xc1e1d0, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/endpoint.go:47 +0x31 fp=0xc20810d620 sp=0xc20810d5c0 github.com/docker/docker/registry.(*Service).Auth(0xc20802e340, 0xc208d91900, 0x2) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/service.go:64 +0x168 fp=0xc20810d730 sp=0xc20810d620 github.com/docker/docker/registry.*Service.AuthÂ·fm(0xc208d91900, 0x7fac53e860a0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/service.go:33 +0x31 fp=0xc20810d750 sp=0xc20810d730 github.com/docker/docker/engine.(*Job).Run(0xc208d91900, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/engine/job.go:90 +0x936 fp=0xc20810d8a0 sp=0xc20810d750 github.com/docker/docker/api/server.postAuth(0xc2080e20d0, 0xc208984c27, 0x4, 0x7fac53ead348, 0xc208d917c0, 0xc20893e000, 0xc20933a6c0, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/api/server/server.go:189 +0x292 fp=0xc20810d9e0 sp=0xc20810d8a0 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1212188 [Bug 1212188] Unable to 'docker login' with 1.6.0-2.el7 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1174354] New: Missing Requires: cadvisor
by Red Hat Bugzilla 02 Dec '15

02 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1174354 Bug ID: 1174354 Summary: Missing Requires: cadvisor Product: Fedora Version: 21 Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: tstclair(a)redhat.com 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, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: k8's has a missing run-time dependency on cadvisor that is not installed when k8's is installed. Version-Release number of selected component (if applicable): 0.6-4.0.git993ef88.fc21 How reproducible: 100% Steps to Reproduce: 1. yum install kubernetes 2. check installation list Actual results: no cadvisor Expected results: install cadvisor -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1135152] New: user: Current not implemented on linux/amd64
by Red Hat Bugzilla 01 Dec '15

01 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1135152 Bug ID: 1135152 Summary: user: Current not implemented on linux/amd64 Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: adam(a)spicenitz.org QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)fedoraproject.org, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: golang seems to be using some cross-compiled components which are causing problems. Specifically, Fedora has exactly the problem described here: http://stackoverflow.com/questions/20609415/cross-compiling-user-current-no… Here is the sample code from that page: package main import ( "fmt" "os/user" ) func main() { fmt.Println(user.Current()) } You can build the sample code and see the problem directly: $ go build ./current.go $ ./current <nil> user: Current not implemented on linux/amd64 Version-Release number of selected component (if applicable): golang-1.2.2-22.fc20.x86_64 How reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1206751] New: Docker with overlay cannot run bash(prevented by SELinx)
by Red Hat Bugzilla 06 Nov '15

06 Nov '15

https://bugzilla.redhat.com/show_bug.cgi?id=1206751 Bug ID: 1206751 Summary: Docker with overlay cannot run bash(prevented by SELinx) Product: Fedora Version: 21 Component: docker-io Severity: high Assignee: ichavero(a)redhat.com Reporter: robberphex(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: the container cannot read .so file in overlay, and cannot relabel the file system. How reproducible: Steps to Reproduce: 1. Add "DOCKER_STORAGE_OPTIONS= --storage-driver=overlay" to /etc/sysconfig/docker-storage, and restart docker service. 2. repull the image(in my case, pull debian:jessie) 3. Run container(sudo docker run -it debian:jessie /bin/bash) Actual results: /bin/bash: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory (preventing by SELinx) Expected results: bash prompt in container Additional info: There is 4 SeLinux Alert: ----1---- SELinux is preventing docker from mount access on the filesystem /. ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin catchall (6.38 confidence) suggests ************************** If you believe that docker should be allowed mount access on the filesystem by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep docker /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:docker_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects / [ filesystem ] Source docker Source Path docker Port <Unknown> Host rp.fedora Source RPM Packages Target RPM Packages filesystem-3.2-28.fc21.x86_64 Policy RPM selinux-policy-3.13.1-105.6.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name rp.fedora Platform Linux rp.fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-28 09:08:17 CST Last Seen 2015-03-28 09:08:17 CST Local ID fcd44130-63b9-4680-9975-4dc6a416b566 Raw Audit Messages type=AVC msg=audit(1427504897.987:739): avc: denied { mount } for pid=1337 comm="docker" name="/" dev="overlay" ino=65132 scontext=system_u:system_r:docker_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1 Hash: docker,docker_t,unlabeled_t,filesystem,mount ----2---- SELinux is preventing docker from unmount access on the filesystem . ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin catchall (6.38 confidence) suggests ************************** If you believe that docker should be allowed unmount access on the filesystem by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep docker /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:docker_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects [ filesystem ] Source docker Source Path docker Port <Unknown> Host rp.fedora Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.6.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name rp.fedora Platform Linux rp.fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-28 09:08:17 CST Last Seen 2015-03-28 09:08:17 CST Local ID c4a57cd0-ae92-4521-ad81-40a5e30a5627 Raw Audit Messages type=AVC msg=audit(1427504897.990:740): avc: denied { unmount } for pid=1337 comm="docker" scontext=system_u:system_r:docker_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1 Hash: docker,docker_t,unlabeled_t,filesystem,unmount ----3---- SELinux is preventing docker from relabelfrom access on the filesystem . ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin file (47.5 confidence) suggests ****************************** If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin catchall (6.38 confidence) suggests ************************** If you believe that docker should be allowed relabelfrom access on the filesystem by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep docker /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:docker_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects [ filesystem ] Source docker Source Path docker Port <Unknown> Host rp.fedora Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.6.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name rp.fedora Platform Linux rp.fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-28 09:08:17 CST Last Seen 2015-03-28 09:08:17 CST Local ID ad86497a-be89-4611-8686-7aa67e73f523 Raw Audit Messages type=AVC msg=audit(1427504897.998:741): avc: denied { relabelfrom } for pid=1337 comm="docker" scontext=system_u:system_r:docker_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1 Hash: docker,docker_t,unlabeled_t,filesystem,relabelfrom ----4---- SELinux is preventing bash from read access on the file /var/lib/docker/overlay/1cbc0c1b2084b5f3c8fdc283032c124f6fb461242cc5b82fb183095a414869b9/root/lib/x86_64-linux-gnu/libncurses.so.5.9. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that bash should be allowed read access on the libncurses.so.5.9 file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep bash /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:svirt_lxc_net_t:s0:c156,c1000 Target Context system_u:object_r:docker_var_lib_t:s0 Target Objects /var/lib/docker/overlay/1cbc0c1b2084b5f3c8fdc28303 2c124f6fb461242cc5b82fb183095a414869b9/root/lib/x8 6_64-linux-gnu/libncurses.so.5.9 [ file ] Source bash Source Path bash Port <Unknown> Host rp.fedora Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.6.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name rp.fedora Platform Linux rp.fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-28 09:08:18 CST Last Seen 2015-03-28 09:08:18 CST Local ID 2a5fbf0f-dc4e-489b-a9ca-2541bb55209e Raw Audit Messages type=AVC msg=audit(1427504898.269:754): avc: denied { read } for pid=10156 comm="bash" name="libncurses.so.5.9" dev="dm-0" ino=2100260 scontext=system_u:system_r:svirt_lxc_net_t:s0:c156,c1000 tcontext=system_u:object_r:docker_var_lib_t:s0 tclass=file permissive=0 Hash: bash,svirt_lxc_net_t,docker_var_lib_t,file,read ----end---- -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1195525] New: Docker socket permissions prevent Cockpit integration
by Red Hat Bugzilla 14 Oct '15

14 Oct '15

https://bugzilla.redhat.com/show_bug.cgi?id=1195525 Bug ID: 1195525 Summary: Docker socket permissions prevent Cockpit integration Product: Fedora Version: 21 Component: docker-io Severity: medium Assignee: lsm5(a)redhat.com Reporter: Benjamin(a)BGRoberts.id.au QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: The removal of docker.socket and the docker user/group mean that docker cannot be used as part of the cockpit console anymore (using non-root accounts). This is because, although users can be added to the dockerroot group, the permissions of the sockets are reset upon docker restart. Version-Release number of selected component (if applicable): docker-io-1.5.0-1.fc21.x86_64 cockpit-0.27-3.fc21.x86_64 / cockpit-head Steps to Reproduce: 1. Add user to dockerroot 2. chown docker socket to root:dockerroot 3. Call a docker command from user (succeeds from CLI and cockpit) 4. restart docker 5. Call a docker command from user (fails from CLI and cockpit) Actual results: Ownership of docker socket are reset to root:root Expected results: Ownership of docker socket should be configurable and compatible with cockpit Additional info: related to https://bugzilla.redhat.com/show_bug.cgi?id=1192848 Relevant change in the rpm spec: "* Fri Jan 16 2015 Lokesh Mandvekar <lsm5(a)fedoraproject.org> - 1.4.1-7 - docker group no longer used or created - no socket activation - config file updates to include info about docker_transition_unconfined boolean" -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1166611] New: Extend golang %files section with golang.org/x directory ownership
by Red Hat Bugzilla 01 Oct '15

01 Oct '15

https://bugzilla.redhat.com/show_bug.cgi?id=1166611 Bug ID: 1166611 Summary: Extend golang %files section with golang.org/x directory ownership Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)fedoraproject.org, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: https://groups.google.com/forum/#!topic/golang-nuts/eD8dh3T9yyA First post: ... This list shows the current base import paths, and their new equivalents. code.google.com/p/go.benchmarks -> golang.org/x/benchmarks code.google.com/p/go.blog -> golang.org/x/blog code.google.com/p/go.crypto -> golang.org/x/crypto code.google.com/p/go.exp -> golang.org/x/exp code.google.com/p/go.image -> golang.org/x/image code.google.com/p/go.mobile -> golang.org/x/mobile code.google.com/p/go.net -> golang.org/x/net code.google.com/p/go.sys -> golang.org/x/sys code.google.com/p/go.talks -> golang.org/x/talks code.google.com/p/go.text -> golang.org/x/text code.google.com/p/go.tools -> golang.org/x/tools ... import paths are being extended for new equivalents starting with "golang.org/x/..." Version-Release number of selected component (if applicable): golang-1.3.99-2.1.4rc1.fc22 How reproducible: Always Steps to Reproduce: 1. rpm -q --provides golang | grep golang.org Actual results: Empty result Expected results: /usr/share/gocode/src/golang.org /usr/share/gocode/src/golang.org/x Additional info: Extend ownership for all branches (at least el6, f20,f21,master) -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1214774] New: Tracker for golang-github-spf13-cobra
by Red Hat Bugzilla 26 Sep '15

26 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214774 Bug ID: 1214774 Summary: Tracker for golang-github-spf13-cobra Product: Fedora Version: rawhide Component: golang-github-rackspace-gophercloud 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-rackspace-gophercloud 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.

1 21

[Bug 1223451] New: Tracker for golang-github-mitchellh-goamz
by Red Hat Bugzilla 26 Sep '15

26 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1223451 Bug ID: 1223451 Summary: Tracker for golang-github-mitchellh-goamz Product: Fedora Version: rawhide Component: golang-github-mitchellh-goamz Severity: low Priority: low 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-mitchellh-goamz 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.

1 17

[Bug 1187077] New: Fedora:latest docker image yum won't update
by Red Hat Bugzilla 16 Sep '15

16 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1187077 Bug ID: 1187077 Summary: Fedora:latest docker image yum won't update Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: cyborg101010(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: I cannot install from or update yum inside Docker. RUN yum install make automake gcc gcc-c++ kernel-devel tar wget ---> Running in 04cdfe47b7ac One of the configured repositories failed (Fedora 21 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable fedora 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=fedora.skip_if_unavailable=true Cannot retrieve metalink for repository: fedora/21/x86_64. Please verify its path and try again Version-Release number of selected component (if applicable): Docker 1.4.1 Fedora:latest How reproducible: Seems rare, but I can find others with the issue (e.g. https://registry.hub.docker.com/_/fedora/ see comment from crackcomm) Steps to Reproduce: 1. Take any examples https://github.com/fedora-cloud/Fedora-Dockerfiles 2. docker build an example 3. Wait for yum update / install Actual results: Yum errors and exits. Expected results: Yum update / install -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1214394] New: docker-io makes the hosts /sys directory read only
by Red Hat Bugzilla 09 Sep '15

09 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214394 Bug ID: 1214394 Summary: docker-io makes the hosts /sys directory read only Product: Fedora Version: rawhide Component: docker-io Severity: medium Assignee: ichavero(a)redhat.com Reporter: pwebster(a)ca.ibm.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: I installed docker-io on RHEL 6.6. If I create a regular container, I suddenly can no longer suspend my machine. I tracked it down to the /sys directory being mounted read-only on the host. Bug 1094198 says that it should be mounted read-only within the container if the container is run as non-privileged, but that should not effect the host. Version-Release number of selected component (if applicable): docker-io-1.4.1-3.el6.x86_64 RHEL 6.6 kernel-2.6.32-504.12.2.el6.x86_64 How reproducible: 100% Steps to Reproduce: Start a docker container: bash$ docker run -ti fedora:latest /bin/bash Outside of docker, run as root: [root@wspwebster log]# echo 7 > /sys/module/cpufreq/parameters/debug -bash: /sys/module/cpufreq/parameters/debug: Read-only file system Actual results: fails to write to /sys anymore. This effects other commands, like pm-suspend (can't suspend my laptop anymore) Expected results: Should be able to write out to the /sys file system as root. Additional info: Version: Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz Version: G5ET90WW (2.50 ) Version: ThinkPad W530 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1161618] New: influxdb: please update to 0.8.5
by Red Hat Bugzilla 03 Sep '15

03 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1161618 Bug ID: 1161618 Summary: influxdb: please update to 0.8.5 Product: Fedora Version: rawhide Component: golang-github-influxdb-influxdb Assignee: jchaloup(a)redhat.com Reporter: ruben(a)rubenkerkhof.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)fedoraproject.org, vbatts(a)redhat.com Thanks for packaging influxdb! Would it be possible to upgrade the package to 0.8.5? It contains some fixes regarding sharding I bumped in to, and also the new collectd plugin would be nice to have. Kind regards, Ruben -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1119282] New: [Regression] Unable to run docker client as non-root user
by Red Hat Bugzilla 03 Sep '15

03 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1119282 Bug ID: 1119282 Summary: [Regression] Unable to run docker client as non-root user Product: Fedora Version: 19 Component: docker-io Assignee: lsm5(a)switzerlandmail.ch Reporter: psavage(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, lsm5(a)switzerlandmail.ch, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Docker used to be able to run it's client as non-root user, allowed things like `docker ps` and `docker run` but since latest update I am unable to do that. Even though the user running the docker command is in the docker group, which previously worked. Version-Release number of selected component (if applicable):docker-io-1.0.0-6.fc19.x86_64 How reproducible: Steps to Reproduce: 1. Run docker ps 2. 3. Actual results: 2014/07/14 13:25:33 Get http:///var/run/docker.sock/v1.12/containers/json: dial unix /var/run/docker.sock: permission denied Expected results: Docker command should run Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1144636] New: Docker fails to start on systems with SELinux and btrfs
by Red Hat Bugzilla 02 Sep '15

02 Sep '15

https://bugzilla.redhat.com/show_bug.cgi?id=1144636 Bug ID: 1144636 Summary: Docker fails to start on systems with SELinux and btrfs Product: Fedora Version: 20 Component: docker-io Severity: urgent Assignee: lsm5(a)fedoraproject.org Reporter: voxadam(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com External Bug ID: Red Hat Bugzilla 1128041 External Bug ID: Red Hat Bugzilla 1128041 Description of problem: The Docker daemon fails to start on systems with SELinux and btrfs Version-Release number of selected component (if applicable): Kernel: 3.16.2-200.fc20.x86_64 #1 SMP Docker: 1.2.0 (2.fc20) libselinux: 2.2.1 (6.fc20) How reproducible: Incredibly so. Steps to Reproduce: 1. Install F20 on btrfs 2. systemctl start docker 3. Bang head against desk Actual results: adam@dekatron  ~/bin  sudo systemctl start docker [sudo] password for adam: Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details. ✘ adam@dekatron  ~/bin  journalctl -xn -- Logs begin at Wed 2014-09-17 14:41:46 PDT, end at Fri 2014-09-19 18:18:26 PDT. -- Sep 19 18:18:18 dekatron.voxadam.com docker[7517]: 2014/09/19 18:18:18 SELinux is not supported with the BTRFS graph driver! Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. Expected results: Docker should start. Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1128041 https://github.com/docker/docker/issues/7952 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1192721] New: Fix debugging - fix runtime-gdb.py
by Red Hat Bugzilla 27 Aug '15

27 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1192721 Bug ID: 1192721 Summary: Fix debugging - fix runtime-gdb.py Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: jan.kratochvil(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 991759 --> https://bugzilla.redhat.com/attachment.cgi?id=991759&action=edit Fedora packaging + runtime-gdb.py fix Description of problem: Currently golang GDB support script is not loaded at all. Load it and fix its obsolete parts. Version-Release number of selected component (if applicable): golang-1.4.1-1.fc22.x86_64 How reproducible: Always. Steps to Reproduce: $ gdb golang-produced binary (gdb) start (gdb) info goroutines (gdb) goroutine 4 bt Actual results: Undefined info command: "goroutines". Try "help info". Expected results: Loading Go Runtime support. (gdb) start [...] (gdb) info goroutines * 1 running fname=runtime.switchtoM faddr=0x437a60 &g=0xc208000120 2 runnable fname=runtime.forcegchelper faddr=0x412010 &g=0xc208000480 3 runnable fname=runtime.bgsweep faddr=0x40dcd0 &g=0xc2080005a0 4 runnable fname=runtime.runfinq faddr=0x40d3f0 &g=0xc2080006c0 (gdb) goroutine 4 bt #0 runtime.runfinq () at /usr/lib/golang/src/runtime/malloc.go:712 #1 0x0000000000439ca1 in runtime.goexit () at /usr/lib/golang/src/runtime/asm_amd64.s:2232 #2 0x0000000000000000 in ?? () Additional info: Probably some interfaces pretty printer there also needs to be fixed. Backtraces need to be fixed etc. https://sourceware.org/gdb/wiki/GoDebugging -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219534] New: Getting docker daemon not running error
by Red Hat Bugzilla 20 Aug '15

20 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219534 Bug ID: 1219534 Summary: Getting docker daemon not running error Product: Fedora EPEL Version: epel7 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: ramesh.reddy(a)bankofamerica.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: Getting docker daemon not running error Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Installed EPEL on 6.5 RHEL 2. Installed docker-io 3. Able to run "docker" command 4. When running "docker run -i -t fedora /bin/bash" command using without root, getting below error FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker.sock <http:///var/run/docker.sock/v1.17/containers/create:%20dial%20unix%20/var/run/docker.sock> : permission denied. Are you trying to connect to a TLS-enabled daemon without TLS? However, with root getting diff error like below for the same command FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host? Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218599] New: docker can no longer copy from inside the container
by Red Hat Bugzilla 20 Aug '15

20 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1218599 Bug ID: 1218599 Summary: docker can no longer copy from inside the container Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: nmavrogi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Created attachment 1022155 --> https://bugzilla.redhat.com/attachment.cgi?id=1022155&action=edit dockerfile reproducer Description of problem: After upgrading docker I can no longer cp from inside a container. I upgraded to docker-io-1.6.0-4.git350a636.fc21.x86_64 and tried docker-io-1.6.0-4.git350a636.fc21.x86_64 as well. Both fail. This is a regression in F21. That worked fine with 1.3.2 How reproducible: Outside the container use: docker cp my_container:/tmp/file-created-in-the-container ./tmp/ FATA[0000] Error response from daemon: Could not find the file ... Using ssh I can verify that the files exist Steps to Reproduce: 0. Copy the attached dockerfile into docker-dir 1. sudo docker build -t test-image docker-dir 2. sudo docker run -P --privileged=true --name xxx-name test-image 3. sudo docker cp xxx-name:/tmp/xxx /tmp/ Actual results: With 1.3.2: nothing. The file is copied. With 1.6.0: FATA[0000] Error response from daemon: Could not find the file /tmp/xxx in container xxx-name Expected results: The file should have been copied. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214464] New: Unable to use --net=container on RHEL 6.6
by Red Hat Bugzilla 20 Aug '15

20 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214464 Bug ID: 1214464 Summary: Unable to use --net=container on RHEL 6.6 Product: Fedora EPEL Version: el6 Component: docker-io Severity: high Assignee: ichavero(a)redhat.com Reporter: pwebster(a)ca.ibm.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: I can't use the --net=container option on a second container. I get an error and the container fails to start Version-Release number of selected component (if applicable): docker-io-1.4.1-3.el6.x86_64 RHEL 6.6 kernel-2.6.32-504.12.2.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start up the first container bash$ docker run -ti --name=target fedora /bin/bash 2. start up the second container in another xterm bash$ docker run -ti --rm --net=container:target fedora /bin/bash Actual results: It spits out an error: setup networking failed to setns current network namespace: invalid argumentFATA[0002] Error response from daemon: Cannot start container ac211304b75a4fca4839739e9769ded6e4fb61aa74bf9e862499aed09b12c3c6: setup networking failed to setns current network namespace: invalid argument Expected results: It just fires up the second container. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1215626] New: Tracker for golang-github-emicklei-go-restful
by Red Hat Bugzilla 19 Aug '15

19 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1215626 Bug ID: 1215626 Summary: Tracker for golang-github-emicklei-go-restful Product: Fedora Version: rawhide Component: golang-github-emicklei-go-restful Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, 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-emicklei-go-restful 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.

1 27

[Bug 1214600] New: Tracker for golang-github-docker-spdystream updates
by Red Hat Bugzilla 19 Aug '15

19 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214600 Bug ID: 1214600 Summary: Tracker for golang-github-docker-spdystream updates Product: Fedora Version: rawhide Component: golang-github-docker-spdystream Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com Blocks: 1211266 Tracker for async updates of golang-github-docker-spdystream 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. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1211266 [Bug 1211266] Tracking bugzilla for kubernetes updates -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1214614] New: Tracker for golang-github-gorilla-context updates
by Red Hat Bugzilla 19 Aug '15

19 Aug '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214614 Bug ID: 1214614 Summary: Tracker for golang-github-gorilla-context updates Product: Fedora Version: rawhide Component: golang-github-gorilla-context 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 Depends On: 1214600 Tracker for async updates of golang-github-gorilla-context 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. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1214600 [Bug 1214600] Tracker for golang-github-docker-spdystream updates -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1147324] New: CVE-2014-7189 golang: TLS client authentication issue fixed in version 1.3.2
by Red Hat Bugzilla 31 Jul '15

31 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1147324 Bug ID: 1147324 Summary: CVE-2014-7189 golang: TLS client authentication issue fixed in version 1.3.2 Product: Security Response Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: mmcallis(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)fedoraproject.org, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com The Go 1.3.2 release fixes the following issue: "The crpyto/tls fix addresses a security bug that affects programs that use crypto/tls to implement a TLS server from Go 1.1 onwards. If the server enables TLS client authentication using certificates (this is rare) and explicitly sets SessionTicketsDisabled to true in the tls.Config, then a malicious client can falsely assert ownership of any client certificate it wishes." Upstream fix: https://code.google.com/p/go/source/detail?r=eae0457c101512f59296538f016274… References: http://seclists.org/oss-sec/2014/q3/749 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1217987] New: docker push to dockerhub does not work (docker 1.16)
by Red Hat Bugzilla 28 Jul '15

28 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1217987 Bug ID: 1217987 Summary: docker push to dockerhub does not work (docker 1.16) Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: spousty(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com 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: -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214602] New: Tracker for golang-github-docker-spdystream updates
by Red Hat Bugzilla 27 Jul '15

27 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1214602 Bug ID: 1214602 Summary: Tracker for golang-github-docker-spdystream updates Product: Fedora Version: rawhide Component: golang-github-gorilla-mux 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-gorilla-mux 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.

1 12

[Bug 1216151] New: Docker fails mounting a volume as readonly on files located under /usr
by Red Hat Bugzilla 21 Jul '15

21 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216151 Bug ID: 1216151 Summary: Docker fails mounting a volume as readonly on files located under /usr Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: yann.robert(a)anantaplex.fr QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com 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 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1176302] New: /var/log/docker incorrectly asserts that kernel 2.6.32* "might be unstable running docker"
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1176302 Bug ID: 1176302 Summary: /var/log/docker incorrectly asserts that kernel 2.6.32* "might be unstable running docker" Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: afoxson(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: The following warning appears in /var/log/docker: "WARNING: You are running linux kernel version 2.6.32-504.1.3.el6.x86_64, which might be unstable running docker. Please upgrade your kernel to 3.8.0." Version-Release number of selected component (if applicable): docker-io-1.3.2-2.el6.x86_64.rpm How reproducible: Consistently. Steps to Reproduce: 1. Run docker in daemon mode. 2. Review /var/log/docker. Actual results: The aforementioned warning appears in /var/log/docker. Expected results: The aforementioned warning not appearing in /var/log/docker. Additional info: This warning is incorrect as per: https://github.com/docker/docker/issues/407#issuecomment-43206662 which states: "Kernels older than 3.8 aren't supported. That means technical support isn't provided and you might run into unexpected behavior, even if it seems like it's working. The only exception is the kernel provided by RHEL6 (2.6.32xxxxxx) which was patched and improved to work properly with Docker." It seems that an environment variable is available for this situation, as per: https://github.com/shykes/docker-dev/commit/2c2a655da14f6de9353454673f2a1c9… which states: "set DOCKER_NOWARN_KERNEL_VERSION=1 to disable the warning for RHEL 6.5" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213258] New: Docker 1.6 needs tar but does not require it
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1213258 Bug ID: 1213258 Summary: Docker 1.6 needs tar but does not require it Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: jpazdziora(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: Starting container fails with fork/exec /usr/bin/tar: no such file or directory Version-Release number of selected component (if applicable): docker-io-1.6.0-0.1.rc6.fc21 How reproducible: Seen once, assume deterministic. Steps to Reproduce: 1. Build an image. 2. Run a container. Actual results: time="2015-04-20T03:35:12-04:00" level=fatal msg="Error response from daemon: Cannot start container 4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29: [8] System error: [/usr/bin/tar -cf /var/lib/docker/tmp/4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29725221613/_run.tar -C /var/lib/docker/devicemapper/mnt/4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29/rootfs/run .] failed: : fork/exec /usr/bin/tar: no such file or directory" Expected results: No error, container runs. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1219703] New: CVE-2015-3629 docker-io: docker: symlink traversal on container respawn allows local privilege escalation [fedora-all]
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219703 Bug ID: 1219703 Summary: CVE-2015-3629 docker-io: docker: symlink traversal on container respawn allows local privilege escalation [fedora-all] Product: Fedora Version: 21 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219058 (CVE-2015-3629) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219058 [Bug 1219058] CVE-2015-3629 docker: symlink traversal on container respawn allows local privilege escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219707] New: CVE-2015-3627 docker-io: docker: insecure opening of file-descriptor 1 leading to privilege escalation [fedora-all]
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219707 Bug ID: 1219707 Summary: CVE-2015-3627 docker-io: docker: insecure opening of file-descriptor 1 leading to privilege escalation [fedora-all] Product: Fedora Version: 21 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219061 (CVE-2015-3627) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219061 [Bug 1219061] CVE-2015-3627 docker: insecure opening of file-descriptor 1 leading to privilege escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219711] New: CVE-2015-3630 docker-io: docker: Read/write proc paths allow host modification & information disclosure [fedora-all]
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219711 Bug ID: 1219711 Summary: CVE-2015-3630 docker-io: docker: Read/write proc paths allow host modification & information disclosure [fedora-all] Product: Fedora Version: 21 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219063 (CVE-2015-3630) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219063 [Bug 1219063] CVE-2015-3630 docker: Read/write proc paths allow host modification & information disclosure -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219715] New: CVE-2015-3631 docker-io: docker: volume mounts allow LSM profile escalation [fedora-all]
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219715 Bug ID: 1219715 Summary: CVE-2015-3631 docker-io: docker: volume mounts allow LSM profile escalation [fedora-all] Product: Fedora Version: 21 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219065 (CVE-2015-3631) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219065 [Bug 1219065] CVE-2015-3631 docker: volume mounts allow LSM profile escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221482] New: Docker 1.6 mounts /var/log/journal/4809557f6c5a83f899a25b507d72c4d5
by Red Hat Bugzilla 15 Jul '15

15 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1221482 Bug ID: 1221482 Summary: Docker 1.6 mounts /var/log/journal/4809557f6c5a83f899a25b507d72c4d5 Product: Fedora Version: 21 Component: docker-io Keywords: Regression Assignee: ichavero(a)redhat.com Reporter: jpazdziora(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, agoldste(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, jeder(a)redhat.com, jpazdziora(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, sdodson(a)redhat.com, thrcka(a)redhat.com, vbatts(a)redhat.com Depends On: 1213385 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1213385 [Bug 1213385] Docker 1.6 mounts /var/log/journal/4809557f6c5a83f899a25b507d72c4d5 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1184710] New: dnsmasq needs to be restarted after reboot for dns to work in a Docker container
by Red Hat Bugzilla 08 Jul '15

08 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1184710 Bug ID: 1184710 Summary: dnsmasq needs to be restarted after reboot for dns to work in a Docker container Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jshepherd(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com External Bug ID: Red Hat Bugzilla 1128208 External Bug ID: Red Hat Bugzilla 1128208 Description of problem: Docker replies on dnsmasq to have 'listen-address' set to the docker bridge, and have bind-interfaces option turned on. However in this configuration dnsmasq has to start after docker in order for DNS to work in a docker container. Version-Release number of selected component (if applicable): docker-io 1.4.0 dnsmasq 2.72 How reproducible: Reboot the system with docker, and dnsmasq enabled. Steps to Reproduce: 1. Ensure docker is using the default dns option of 172.17.42.1 2. Use the attached dnsmasq.conf 3. Reboot the system 4. Launch a docker container: `docker run -i -t centos /usr/bin/ping www.redhat.com` Actual results: Cannot resolve hostname Expected results: Response from 'akamai' or similar Additional info: See related issue #1128208 I tried added a systemd 'After' for dnsmasq on docker.service, but it doesn't seem to be honoured by systemd. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1108349] New: remove golang-github-syndtr-gocapability from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108349 Bug ID: 1108349 Summary: remove golang-github-syndtr-gocapability from epel7 Product: Fedora EPEL Version: epel7 Component: golang-github-syndtr-gocapability Assignee: vbatts(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, vbatts(a)redhat.com Description of problem: remove this package from epel7 as it's now available in rhel7 proper. Version-Release number of selected component (if applicable): golang-github-syndtr-gocapability-0-0.5.git3454319.el7 Additional info: retired from dist-git: http://pkgs.fedoraproject.org/cgit/golang-github-syndtr-gocapability.git/tr… For pkgdb, Vincent could you run this for the epel7 branch (I'm not an admin for this one): pkgdb-cli orphan --retire golang-github-syndtr-gocapability epel7 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1108337] New: remove golang-googlecode-sqlite from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108337 Bug ID: 1108337 Summary: remove golang-googlecode-sqlite from epel7 Product: Fedora EPEL Version: epel7 Component: golang-googlecode-sqlite Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, vbatts(a)redhat.com Description of problem: this package should be removed from epel7 as it's now available in rhel7 proper Version-Release number of selected component (if applicable): golang-googlecode-sqlite-0-0.9.hg74691fb6f837.el7 Additional info: retired from dist-git: http://pkgs.fedoraproject.org/cgit/golang-googlecode-sqlite.git/tree/?h=epe… orphaned in pkgdb: https://admin.fedoraproject.org/pkgdb/package/golang-googlecode-sqlite/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1108270] New: remove golang-googlecode-net from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108270 Bug ID: 1108270 Summary: remove golang-googlecode-net from epel7 Product: Fedora EPEL Version: epel7 Component: golang-googlecode-net Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Description of problem: this package should be removed from epel7 as it's available in rhel7 proper Version-Release number of selected component (if applicable): golang-googlecode-net-0-0.13.hg84a4013f96e0.el7 Additional info: epel7 orphaned: https://admin.fedoraproject.org/pkgdb/package/golang-googlecode-net/ retired from dist-git: http://pkgs.fedoraproject.org/cgit/golang-googlecode-net.git/tree/?h=epel7 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1108249] New: remove golang-github-gorilla-mux from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108249 Bug ID: 1108249 Summary: remove golang-github-gorilla-mux from epel7 Product: Fedora EPEL Version: epel7 Component: golang-github-gorilla-mux Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Description of problem: remove this package from epel7 as it exists in rhel7 proper Version-Release number of selected component (if applicable): golang-github-gorilla-mux-0-0.13.git136d54f.el7 Additional info: retired from dist-git: http://pkgs.fedoraproject.org/cgit/golang-github-gorilla-mux.git/tree/?h=ep… orphaned in pkgdb: https://admin.fedoraproject.org/pkgdb/package/golang-github-gorilla-mux/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1108248] New: remove golang-github-gorilla-context from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108248 Bug ID: 1108248 Summary: remove golang-github-gorilla-context from epel7 Product: Fedora EPEL Version: epel7 Component: golang-github-gorilla-context Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com Description of problem: this package should be removed from epel7 as it exists in RHEL7 proper Version-Release number of selected component (if applicable): golang-github-gorilla-context-0-0.23.gitb06ed15.el7 Additional info: retired from dist-git: http://pkgs.fedoraproject.org/cgit/golang-github-gorilla-context.git/tree/?… orphaned in pkgdb: https://admin.fedoraproject.org/pkgdb/package/golang-github-gorilla-context/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1108244] New: remove golang-github-kr-pty from epel7
by Red Hat Bugzilla 03 Jul '15

03 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=1108244 Bug ID: 1108244 Summary: remove golang-github-kr-pty from epel7 Product: Fedora EPEL Version: epel7 Component: golang-github-kr-pty Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com Description of problem: Remove this package from epel7 as exists in RHEL7 proper Version-Release number of selected component (if applicable): golang-github-kr-pty-0-0.19.git67e2db2.el7 Additional info: retired from dist-git http://pkgs.fedoraproject.org/cgit/golang-github-kr-pty.git/tree/?h=epel7 and orphaned from pkgdb https://admin.fedoraproject.org/pkgdb/package/golang-github-kr-pty/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1100502] New: golang-1.2.2-2 update breaks GOROOT path
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1100502 Bug ID: 1100502 Summary: golang-1.2.2-2 update breaks GOROOT path Product: Fedora Version: 20 Component: golang Assignee: adam(a)spicenitz.org Reporter: porjo38(a)yahoo.com.au QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Since updating to golang-1.2.2-2, I get error "go: cannot find GOROOT directory: /usr/lib64/golang" when trying to run a go program e.g. "go run main.go" Adding a symbolic link fixes the issue: ln -s /usr/lib/golang/ /usr/lib64/golang -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1099732] New: go install fails if cgo is used
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1099732 Bug ID: 1099732 Summary: go install fails if cgo is used Product: Fedora Version: 20 Component: golang Assignee: adam(a)spicenitz.org Reporter: davidb(a)davidb.org QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 897821 --> https://bugzilla.redhat.com/attachment.cgi?id=897821&action=edit Example program to provoke bug Description of problem: 'go install' tries to compile runtime/cgo.a and install it in /usr/lib when the source makes use of Cgo. Version-Release number of selected component (if applicable): golang-src-1.2.2-2.fc20.noarch golang-1.2.2-2.fc20.x86_64 golang-pkg-linux-amd64-1.2.2-2.fc20.noarch golang-pkg-bin-linux-amd64-1.2.2-2.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Create directory with src/bug1/hello.go containing the attached file. 2. GOPATH=$(PWD) /usr/bin/go install bug1 Actual results: go install runtime/cgo: open /usr/lib/golang/pkg/linux_amd64/runtime/cgo.a: permission denied Expected results: Produces bin/bug1, which when run prints hello world. This worked fine with 1.2.1 (before today's update). Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1096293] New: `docker start` doesn't fail on started container
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1096293 Bug ID: 1096293 Summary: `docker start` doesn't fail on started container Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Depends On: 1090071 +++ This bug was initially created as a clone of Bug #1090071 +++ Description of problem: On older (0.9) docker, the `docker start $running_container` failed. The new 0.10.2 version just prints the container name and proceeds. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.10.0-2.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. docker run -i -t -name test fedora bash 2. docker start test Actual results: [root@t530 ~]# docker start test test [root@t530 ~]# echo &? 0 Expected results: [root@t530 ~]# docker start test Error: Cannot start container test: The container 429d709bc86c037b09e9f74dfab40aa33dc19bcf3109daf3f5b2fbbd3c6df297 is already running. 2014/04/22 15:29:28 Error: failed to start one or more containers [root@t530 ~]# echo &? 1 --- Additional comment from Lukas Doktor on 2014-05-05 03:38:57 EDT --- Upstream Docker version 0.10.0, build dc9c28f/0.10.0 has the same issue (silently passes even thought the container was already running) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1090071 [Bug 1090071] `docker start` doesn't fail on started container -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1090071] New: `docker start` doesn't fail on started container
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1090071 Bug ID: 1090071 Summary: `docker start` doesn't fail on started container Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: On older (0.9) docker, the `docker start $running_container` failed. The new 0.10.2 version just prints the container name and proceeds. Version-Release number of selected component (if applicable): docker-io-0.10.0-2.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. docker run -i -t -name test fedora bash 2. docker start test Actual results: [root@t530 ~]# docker start test test [root@t530 ~]# echo &? 0 Expected results: [root@t530 ~]# docker start test Error: Cannot start container test: The container 429d709bc86c037b09e9f74dfab40aa33dc19bcf3109daf3f5b2fbbd3c6df297 is already running. 2014/04/22 15:29:28 Error: failed to start one or more containers [root@t530 ~]# echo &? 1 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1140398] New: Catastrophic failure saving large images
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1140398 Bug ID: 1140398 Summary: Catastrophic failure saving large images Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: lsm5(a)fedoraproject.org Reporter: briemers(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Large docker images are saved written first to temp. As such when one does a "docker save" for a large image the save process will error out with a disk full error. Afterwards, there will be mounting error if attempting to save the image again after resizing tmp. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create an image much larger than your /tmp space 2. Attempt to save 3. Actual results: [briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:41:23 Error: write /tmp/docker-export-336322967/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38/layer.tar: no space left on device [briemers@briemersw staging]$ sudo mount -o remount,size=20g /tmp [sudo] password for briemers: [briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:43:25 Error: Error mounting '/dev/mapper/docker-253:2-2097434-dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38' on '/var/lib/docker/devicemapper/mnt/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38': device or resource busy [briemers@briemersw staging]$ sudo service docker restart Redirecting to /bin/systemctl restart docker.service [briemers@briemersw staging]$ docker save -o /data/oracle-xe-prod.dimg oracle-xe-prod 2014/09/10 16:43:52 Error: Error mounting '/dev/mapper/docker-253:2-2097434-dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38' on '/var/lib/docker/devicemapper/mnt/dd28f4e8cb55517c4a97560a6adc9d2032b9fdfe4fb744857648067f66125a38': device or resource busy Expected results: I would not expect the process to need massive amounts of /tmp space, if so it should have an option to specify where the tmp files are written. Also, the process needs to clean-up it's locks so subsiquent commands don't fail. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1096269] New: lost signals when sending lots of signals using --sig-proxy to docker
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1096269 Bug ID: 1096269 Summary: lost signals when sending lots of signals using --sig-proxy to docker Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1087700 +++ This bug was initially created as a clone of Bug #1087700 +++ Description of problem: When I send lots of signals to the running docker with --sig-proxy (actual kill signals, not `docker kill`), most of them got lost. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. for AAA in `seq 1 32`; do [ $AAA -ne 9 ] && [ $AAA -ne 20 ] && [ $AAA -ne 19 ] && kill -s $AAA $PID; done Actual results: Output of the docker is: Received 1, ignoring... Received 2, ignoring... Expected results: Messages for all of the `Received $NUM, ignoring...` printed (order doesn't matter) Additional info: Skipping 9, 19, 20 as they are a bit too special.. --- Additional comment from Lukas Doktor on 2014-05-05 04:10:09 EDT --- The same results with upstream docker dc9c28f/0.10.0: Output: Received 1, ignoring... [debug] stdcopy.go:111 framesize: 24 Received 2, ignoring... Daemon output: 2014/05/05 10:08:45 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=HUP [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, HUP) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, HUP) = OK (0) 2014/05/05 10:08:45 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=INT [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, INT) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, INT) = OK (0) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087700 [Bug 1087700] lost signals when sending lots of signals using --sig-proxy to docker -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1087697] New: man page inaccuracy about --sig-proxy and --tty
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087697 Bug ID: 1087697 Summary: man page inaccuracy about --sig-proxy and --tty Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: Hi guys, the man page states: --sig-proxy=true: Proxify all received signal to the process (even in non-tty mode) But the real behavior is, that sig-proxy doesn't work when --tty=true. It should be mentioned in there, taht --sig-proxy is incompatible with --tty. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. man docker Actual results: man page says it works even in non-tty Expected results: man page warns that --tty can't be used with --sig-proxy How to verify: 1. docker run --tty=true -i --rm fedora bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps -ax | grep docker 3. kill -SIGUSR1 $PID 4. (with --tty=true no signals are received, when you try the same with --tty=false, signals are proxified and messages are displayed) -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1140405] New: systemctl start docker fails because systemd continuously restarts the daemon
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1140405 Bug ID: 1140405 Summary: systemctl start docker fails because systemd continuously restarts the daemon Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)fedoraproject.org Reporter: a.badger(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: I've installed docker for the first time and tried to start it with "systemctl start docker". The systemctl command returns successfully but then trying to run docker client commands against the daemon timed out. After some poking around I discovered that systemd was starting docker. Docker was taking quite a while to do various initialization tasks including invoking mkfs. systemd decided that docker was unresponsive and terminated it and then restarted it. Because mkfs hadn't finished, docker had to try running mkfs again. This cycle kept continuing and would probably have prevented docker from fully starting up forever. I worked around the problem by telling systemd not to start docker, running the docker daemon manually from a shell, waiting until the mkfs had completed, then shutting down my daemon and rerunning systemctl start docker. After that, the docker service runs fine. Version-Release number of selected component (if applicable): docker-io-1.2.0-2.fc20.x86_64 How reproducible: Everytime for me until after I ran docker as a daemon manually. I don't know how to reproduce once docker has initialized (Probably removing some file or volume but I don't know what it would be). Steps to Reproduce: 1. On a system that hasn't had docker running before 2. yum install docker-io 3. systemctl start docker 4. watch the output of systemctl status docker -l Actual results: systemctl status docker -l will report that docker is in state Activating for several minutes, then show that systemd decided docker wasn't responding, terminate it, and restart. The -l output will also show that docker is running mkfs for most of that time and is still running it when docker is terminated. Expected results: systemctl status docker -l will show that the state has gone to active (running) Additional info: * My filesystem is ext4. The docker initialization is running mkfs.ext4 * I'm using a 4-5 year old laptop with platter HDs. A faster machine or SSD drives might run mkfs quickly enough to not see this issue. * This might be "fixed" by adding some documentation that says to perform certain steps to initialize docker before running systemctl start docker rather than changing docker code to finish initialization sooner. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1123057] New: warning: file /usr/bin/gofmt: remove failed: No such file or directory while removing golang packages
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1123057 Bug ID: 1123057 Summary: warning: file /usr/bin/gofmt: remove failed: No such file or directory while removing golang packages Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: dominik(a)greysector.net QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)fedoraproject.org, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: There are two warnings while removing golang-pkg-bin-linux-amd64 package: warning: file /usr/bin/gofmt: remove failed: No such file or directory warning: file /usr/bin/go: remove failed: No such file or directory Version-Release number of selected component (if applicable): 1.2.2-7.fc20 How reproducible: Always Steps to Reproduce: 1. yum install golang 2. yum remove golang\* Actual Results: # yum remove golang\* Loaded plugins: changelog, langpacks Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.2.2-7.fc20 will be erased ---> Package golang-pkg-bin-linux-amd64.x86_64 0:1.2.2-7.fc20 will be erased ---> Package golang-pkg-linux-amd64.noarch 0:1.2.2-7.fc20 will be erased ---> Package golang-src.noarch 0:1.2.2-7.fc20 will be erased --> Finished Dependency Resolution [...] Running transaction (shutdown inhibited) Erasing : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 1/4 Erasing : golang-pkg-bin-linux-amd64-1.2.2-7.fc20.x86_64 2/4 warning: file /usr/bin/gofmt: remove failed: No such file or directory warning: file /usr/bin/go: remove failed: No such file or directory Erasing : golang-1.2.2-7.fc20.x86_64 3/4 Erasing : golang-src-1.2.2-7.fc20.noarch 4/4 Verifying : golang-src-1.2.2-7.fc20.noarch 1/4 Verifying : golang-1.2.2-7.fc20.x86_64 2/4 Verifying : golang-pkg-bin-linux-amd64-1.2.2-7.fc20.x86_64 3/4 Verifying : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 4/4 Removed: golang.x86_64 0:1.2.2-7.fc20 golang-pkg-bin-linux-amd64.x86_64 0:1.2.2-7.fc20 golang-pkg-linux-amd64.noarch 0:1.2.2-7.fc20 golang-src.noarch 0:1.2.2-7.fc20 Expected Results: no warning about missing files Additional Information: It looks like the links maintained by update-alternatives are not marked as %ghost in the spec file: [...] ifarch x86_64 %files pkg-bin-linux-amd64 %{goroot}/bin/linux_amd64/ # binary executables %{_bindir}/go %{_bindir}/gofmt [...] This is required by the Alternatives guideline: https://fedoraproject.org/wiki/Packaging:Alternatives . -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1075232] New: 0.9.0 Adds virtual interface, NetworkManager attempts to assign dhcp address to it
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1075232 Bug ID: 1075232 Summary: 0.9.0 Adds virtual interface, NetworkManager attempts to assign dhcp address to it Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: admiller(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Created attachment 873221 --> https://bugzilla.redhat.com/attachment.cgi?id=873221&action=edit snippet from /var/log/messages for my laptop around the virtual interface events Description of problem: When you install docker-io-0.9.0 on Fedora 20, it creates a new virtual interface 13: vethf3e3: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP group default qlen 1000 link/ether 1a:9c:40:61:1e:8b brd ff:ff:ff:ff:ff:ff inet6 fe80::189c:40ff:fe61:1e8b/64 scope link valid_lft forever preferred_lft forever Something (I'm thinking dbus or udev) causes NetworkManager to launch dhclient for the new interface, and if you're running with a Desktop Environment this causes a visual change to the NM applet which can be confusing. It doesn't ever do anything, NM eventually times out and gives up and this doesn't appear to impact docker's functionality at all (or at least not yet in my tests have I found an issue, networking works fine). Version-Release number of selected component (if applicable): docker-io-0.9.0-2.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. yum install docker-io #on a machine with a GUI/DE up and running with NetworkManager Actual results: NetworkManager attempts to get a dhcp lease on the new virtual interface. Expected results: NetworkManager probably shouldn't attempt to get a dhcp lease on the new virtual interface, this seems odd. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1221688] New: Docker fails mounting a volume as readonly on files located under /usr
by Red Hat Bugzilla 23 Jun '15

23 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1221688 Bug ID: 1221688 Summary: Docker fails mounting a volume as readonly on files located under /usr Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Severity: high Priority: high Assignee: dwalsh(a)redhat.com Reporter: jhunsaker(a)redhat.com QA Contact: lsu(a)redhat.com CC: adimania(a)gmail.com, admiller(a)redhat.com, bugzilla.redhat.com(a)trancecode.co.uk, dustymabe(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, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com, yann.robert(a)anantaplex.fr Depends On: 1216151 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. ------------------------------------------- Cloning this to RHEL as I didn't see a RHEL BZ for this. This also affects RHEL Atomic Host 7.1.2. Version: docker-1.6.0-11.el7.x86_64 How reproducible: 100% Steps to reproduce: 1. Use the :ro parameter when volume mounting something like /etc/localtime to a container Actual results: # docker run --rm -ti -v /etc/localtime:/etc/localtime:ro rhel7 /bin/bash Timestamp: 2015-05-14 09:24:34.832162133 -0400 EDT 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: FATA[0002] Error response from daemon: Cannot start container 7be2ae04a120232345b5edbf18e487965b5418bb1ee9354e406d7b9f675c6091: [8] System error: Relabeling content in /usr is not allowed. Excepted results: Container should start normally Additional notes: As mentioned in the Fedora bug, removing the :ro will allow the container to start, however this is not desirable for things like /etc/localtime as we don't want the container to be able to change that. 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 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218639] New: docker push to dockerhub does not work (docker 1.16)
by Red Hat Bugzilla 23 Jun '15

23 Jun '15

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-no… --- 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.

1 14

[Bug 1214619] New: Tracker for golang-github-onsi-ginkgo
by Red Hat Bugzilla 20 Jun '15

20 Jun '15

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.

1 19

[Bug 1033606] New: Failed to connect to network from Docker container
by Red Hat Bugzilla 17 Jun '15

17 Jun '15

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.

1 68

[Bug 1215336] New: godoc uses invalid path for documentation
by Red Hat Bugzilla 04 Jun '15

04 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1215336 Bug ID: 1215336 Summary: godoc uses invalid path for documentation Product: Fedora Version: 21 Component: golang Severity: low Assignee: vbatts(a)redhat.com Reporter: eugene.yudin(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Command "godoc" doesn't show documentation. Version-Release number of selected component (if applicable): golang-godoc.x86_64 1:0-1.0.hgd32b5854c941.fc21 How reproducible: Always. Steps to Reproduce: $ godoc fmt Println 2015/04/25 18:00:38 open /usr/lib/golang/src/pkg/fmt: no such file or directory Workaround: # cd /usr/lib/golang/src/ # ln -s . pkg -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222416] New: etcd-v2.0.11 is available
by Red Hat Bugzilla 04 Jun '15

04 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1222416 Bug ID: 1222416 Summary: etcd-v2.0.11 is available Product: Fedora Version: rawhide Component: etcd Keywords: FutureFeature, Triaged Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: avagarwa(a)redhat.com, eparis(a)redhat.com, extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lacypret(a)gmail.com, lemenkov(a)gmail.com, lsm5(a)redhat.com, upstream-release-monitoring(a)fedoraproject.org, walters(a)redhat.com Latest upstream release: v2.0.11 Current version/release in rawhide: 2.0.10-1.fc23 URL: https://github.com/coreos/etcd 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.

1 11

[Bug 1160833] New: Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1160833 Bug ID: 1160833 Summary: Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable Product: Fedora Version: 21 Component: docker-io Severity: high Assignee: lsm5(a)fedoraproject.org Reporter: znmeb(a)znmeb.net QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: Multiple problems with Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable Version-Release number of selected component (if applicable): Atomic Images beta Steps to Reproduce: 1. Browse to http://fedoraproject.org/en/get-prerelease#cloud. 2. Attempt to download and discover broken link to qcow2 and raw disk images on the beta release page. 3. Find, download, verify checksum of images at http://mirror.pnl.gov/fedora/linux/releases/test/21-Beta/Cloud/Images/x86_6… 4. Prepare an initialization ISO file as described in http://www.projectatomic.io/docs/quickstart/ and https://www.technovelty.org//linux/running-cloud-images-locally.html. Note that said documentation a. Is *not* part of the Fedora documentation, which is something I expect for something carrying the "Fedora Cloud" brand, and b. Nowhere is it *explicitly* stated that the username is "fedora" or that once you log in as "fedora", "sudo su -" works to get you into "root" on the console. 5. Log in as "fedora", type "sudo su -" and type "docker ps". Actual results: '-bash: docker: command not found' Expected results: 1. Working links on the beta release page 2. Fedora-branded documentation with the username and how to obtain root. 3. Docker installed and ready to create images and containers. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1187649] New: Fedora:latest docker image d-bus unknown error -1
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1187649 Bug ID: 1187649 Summary: Fedora:latest docker image d-bus unknown error -1 Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: cyborg101010(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: When trying to use anything that relies on D-Bus, on Fedora:latest, you get the error: Failed to get D-Bus connection: Unknown error -1 How reproducible: 100% Steps to Reproduce: 1. Attach to Fedora:latest 2. yum install postgresql-server -y 3. systemctl start postgresql Actual results: Failed to get D-Bus connection: Unknown error -1 Expected results: Systemd starts postgres Additional info: It's not just postgres, I've tried with others. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1216153] New: Docker daemon runs in shared mount namespace
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216153 Bug ID: 1216153 Summary: Docker daemon runs in shared mount namespace Product: Fedora EPEL Version: el6 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: michaeljameswells+redhatbugzilla(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: The docker daemon is run in a shared mount namespace, causing problems when restarting the docker service. This prevents starting up containers where mounts remain in place. Version-Release number of selected component (if applicable): 1.5.0-1.el6 How reproducible: Always Steps to Reproduce: 1. docker run -d --name test centos sleep infinity 2. service docker restart 3. docker start test Actual results: Error response from daemon: Cannot start container test: Error getting container 0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77 from driver devicemapper: Error mounting '/dev/mapper/docker-253:0-2097716-0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77' on '/var/lib/docker/devicemapper/mnt/0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77': device or resource busy FATA[0000] Error: failed to start one or more containers Expected results: Container to start. Additional info: A merged pull request containing updated sysvinit script is found here: https://github.com/docker/docker/pull/10225 It was merged prior to the 1.5.0 release and involves running "unshare -m" when starting the docker daemon to place it into its own mount namespace. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216265] New: docker exec -it bash cannot start a shell session
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216265 Bug ID: 1216265 Summary: docker exec -it bash cannot start a shell session Product: Fedora Version: 22 Component: docker-io Severity: high Assignee: ichavero(a)redhat.com Reporter: robberphex(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: `docker exec -it <name> /bin/bash` cannot work Version-Release number of selected component (if applicable): $ uname -a Linux rp.fedora 4.0.0-0.rc5.git4.1.fc22.x86_64 #1 SMP Fri Mar 27 13:51:23 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ sudo docker version Client version: 1.6.0 Client API version: 1.18 Go version (client): go1.4.2 Git commit (client): 0591dce/1.6.0 OS/Arch (client): linux/amd64 Server version: 1.6.0 Server API version: 1.18 Go version (server): go1.4.2 Git commit (server): 0591dce/1.6.0 OS/Arch (server): linux/amd64 How reproducible: Steps to Reproduce: 1. `sudo docker run --name some-nginx -d nginx:1.7` 2. `sudo docker exec -it some-nginx /bin/bash` Actual results: <no output> Expected results: start a bash session Additional info: `sudo docker exec -it some-nginx echo hello` also have no ouput. but `sudo docker exec some-nginx echo hello` get the output('hello'). -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224417] New: add selinux label for /var/lib/kubelet
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1224417 Bug ID: 1224417 Summary: add selinux label for /var/lib/kubelet Product: Fedora Version: rawhide Component: docker-io Assignee: ichavero(a)redhat.com Reporter: eparis(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com can we get system_u:object_r:svirt_sandbox_file_t:s0 added as the filecontext for /var/lib/kubelet to the docker-selinux package? can/should we maybe break docker-selinux into it's own package? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1096286] New: "docker top all" doesn't show processes when --tty=false
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1096286 Bug ID: 1096286 Summary: "docker top all" doesn't show processes when --tty=false Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1088259 +++ This bug was initially created as a clone of Bug #1088259 +++ After using the same magic required for the upstream docker 0.10 this behaves the same on RHEL docker-0.10.0-8.el7.x86_64 Description of problem: Hi guys, when I run docker with --tty=false, the `docker top $NAME all` doesn't show any processes (just headers). When using only `docker top $NAME` it shows them... Also the `ps` command inside container works, but `ps all` does not. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.0-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -i --tty=false fedora bash 2. docker logs $NAME Actual results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND Expected results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 24006 23954 20 0 11732 540 - R pts/14 0:00 bash --- Additional comment from Lukas Doktor on 2014-05-05 03:41:35 EDT --- Can't reproduce with the upstream Docker version 0.10.0, build dc9c28f/0.10.0 top doesn't work at all (due of https://bugzilla.redhat.com/show_bug.cgi?id=1088125 ) --- Additional comment from Lukas Doktor on 2014-05-05 03:46:07 EDT --- OK I moved it to the old cgroup location and the results are the same. So booth, fedora docker-io-0.9.0-3.fc20.x86_64 and upstream dc9c28f/0.10.0 are unable to list processes using `all` argument in non-tty mode. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1088259 [Bug 1088259] "docker top all" doesn't show processes when --tty=false -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1088259] New: "docker top all" doesn't show processes when --tty=false
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1088259 Bug ID: 1088259 Summary: "docker top all" doesn't show processes when --tty=false Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: Hi guys, when I run docker with --tty=false, the `docker top $NAME all` doesn't show any processes (just headers). When using only `docker top $NAME` it shows them... Also the `ps` command inside container works, but `ps all` does not. Version-Release number of selected component (if applicable): docker-io-0.9.0-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -i --tty=false fedora bash 2. docker logs $NAME Actual results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND Expected results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 24006 23954 20 0 11732 540 - R pts/14 0:00 bash -- You are receiving this mail because: You are on the CC list for the bug.

1 29

Broken dependencies: docker-io
by Fedora Koji Build System 30 May '15

30 May '15

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.

1 0

[Bug 1111189] New: yumBackend started with each `docker start`
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1111189 Bug ID: 1111189 Summary: yumBackend started with each `docker start` Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Hello guys, today I noticed 100% utilization followed by each `docker run` or `docker start`. It wasn't caused by the docker itself, but with each instance, yumBackend is executed. It never happened with older version. 4806 ? RN 0:00 /usr/bin/python /usr/share/PackageKit/helpers/yum/yuBackend.py get-updates none Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -t -i fedora bash 2. top 3. ps ax |grep yum Actual results: yumBackend is started and takes couple of secconds in 100% utilization 4806 ? RN 0:00 /usr/bin/python /usr/share/PackageKit/helpers/yum/yuBackend.py get-updates none Expected results: Apart from container no other processes should be started. (I can run `docker run -t -i fedora bash -c exit` which finishes immediately and the only process using cpu is the yumBackend process) Additional info: I tried executing `busybox sh`, `bash -c exit`, .... I even rebooted the machine but the results are the same. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1159935] "docker events --until" reports the events created even after the specified timestamp
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 Daniel Walsh <dwalsh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2015-05-29 09:17:53 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159935] "docker events --until" reports the events created even after the specified timestamp
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #8 from Fedora End Of Life <endoflife(a)fedoraproject.org> --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1102751] New: Got "Error running removeDevice" after kill -9 docker
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1102751 Bug ID: 1102751 Summary: Got "Error running removeDevice" after kill -9 docker 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: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: While I was playing with Docker today, I found interesting behavior: When you 'kill -9' the 'docker -d' process, then this happens: 1. The 'docker -d' process gets killed ;-) 2. All containers gets killed 3. The 'docker -d' restarts, because of Restart=on-failure Now, while all this is expected and OK, I get this when I tried to 'restart' the container that was killed in 2): May 29 13:24:56 ip-10-146-193-102 systemd[1]: Starting Container origin-db-1... May 29 13:24:56 ip-10-146-193-102 sh[19731]: Reusing b80104263de02f39bbc6d742c977ddadecb0660f5c50386eaf1cf645f3515b9c May 29 13:25:07 ip-10-146-193-102 docker[19739]: Error: Cannot destroy container origin-db-1: Driver devicemapper failed to remove root filesystem e536cf328e0083e2414c750434deb1127517d00399fddac84903825d6f003787: Error running removeDevice May 29 13:25:07 ip-10-146-193-102 docker[19739]: 2014/05/29 13:25:07 Error: failed to remove one or more containers May 29 13:25:07 ip-10-146-193-102 gear[21193]: user: unknown user ctr-origin-db-1 May 29 13:25:09 ip-10-146-193-102 docker[21192]: 2014/05/29 13:25:09 Error: Cannot start container bd1a88a35e84ef6d71fa3e1df0b4e2998318dfed6d60fd3ae381567fff2ac2a3: Cannot find child for /origin-db-1 May 29 13:25:09 ip-10-146-193-102 systemd[1]: ctr-origin-db-1.service: main process exited, code=exited, status=1/FAILURE Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start up some containers 2. kill -9 (the 'docker -d' process pid) 3. Try to start the dead container again 4. Get the error above. Actual results: Expected results: Containers should be successfully started back. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1087700] New: lost signals when sending lots of signals using --sig-proxy to docker
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087700 Bug ID: 1087700 Summary: lost signals when sending lots of signals using --sig-proxy to docker Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: When I send lots of signals to the running docker with --sig-proxy (actual kill signals, not `docker kill`), most of them got lost. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. for AAA in `seq 1 32`; do [ $AAA -ne 9 ] && [ $AAA -ne 20 ] && [ $AAA -ne 19 ] && kill -s $AAA $PID; done Actual results: Output of the docker is: Received 1, ignoring... Received 2, ignoring... Expected results: Messages for all of the `Received $NUM, ignoring...` printed (order doesn't matter) Additional info: Skipping 9, 19, 20 as they are a bit too special.. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1093000] New: Unable to save an image to a tar archive
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1093000 Bug ID: 1093000 Summary: Unable to save an image to a tar archive Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lslebodn(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: I tried to dump content of docker image to a tarball with command "docker save" It failed with error message "no space left on device" Version-Release number of selected component (if applicable): I was able to reproduce problem with docker-io from stable repository and with docker-io from updates-testing [root@vm-169 docker]# rpm -q docker-io docker-io-0.9.1-1.fc20.x86_64 or docker-io-0.10.0-2.fc20.x86_64 How reproducible: Allways Steps to Reproduce: 1. Create big docker image (e.g. 1.8 GiB) [root@vm-169 docker-freeipa]# docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE big_image latest b366efe500de 57 minutes ago 1.778 GB fedora 20 b7de3133ff98 5 days ago 372.7 MB 2. save docker image to tarball [root@vm-169 docker]# docker save big_image > big_image.tar Actual results: [root@vm-169 docker]# docker save big_image > big_image.tar 2014/04/30 12:39:38 Error: write /docker-export-085323451/934d868afd0a79629df2cad704cbc1ed9344654625569263a630933d2785de57/layer.tar: no space left on device [root@vm-169 docker]# file big_image.tar big_image.tar: empty [root@vm-169 docker]# ls -l big_image.tar -rw-r--r--. 1 root root 0 Apr 30 13:41 big_image.tar Expected results: File big_image.tar should not be empty and should contain data from docker image with name big_image Additional info: Directory /tmp should be used for creating small temporary files, because it is mounted on tmpfs. I think it would be better to use /var/tmp in this case. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1010369] golang test suite fails on mssing zoneinfo.zip file
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1010369 --- Comment #1 from Fedora End Of Life <endoflife(a)fedoraproject.org> --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220163] New: Tracker for golang-github-syndtr-goleveldb
by Red Hat Bugzilla 26 May '15

26 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1220163 Bug ID: 1220163 Summary: Tracker for golang-github-syndtr-goleveldb Product: Fedora Version: rawhide Component: golang-github-syndtr-goleveldb Severity: low Priority: low 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-syndtr-goleveldb 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.

1 10

[Bug 1210336] New: cAdvisor fails to start because -samples
by Red Hat Bugzilla 25 May '15

25 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1210336 Bug ID: 1210336 Summary: cAdvisor fails to start because -samples Product: Fedora Version: 22 Component: cadvisor Assignee: jchaloup(a)redhat.com Reporter: stefw(a)redhat.com 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 Description of problem: cAdvisor fails to start because of the --samples argument: Apr 09 15:17:51 falcon.thewalter.lan cadvisor[5117]: flag provided but not defined: -samples Apr 09 15:17:51 falcon.thewalter.lan cadvisor[5117]: Usage of /usr/bin/cadvisor: ... Version-Release number of selected component (if applicable): cadvisor-0.10.1-0.1.gitef7dddf.fc22.x86_64 How reproducible: Every time Steps to Reproduce: 1. systemctl start cadvisor -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219972] New: Tracker for golang-github-docker-gorilla-mux
by Red Hat Bugzilla 25 May '15

25 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219972 Bug ID: 1219972 Summary: Tracker for golang-github-docker-gorilla-mux Product: Fedora Version: rawhide Component: cadvisor Severity: low Priority: low Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com 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 Tracker for async updates of cadvisor 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.

1 9

[Bug 1216096] New: Hard coded /tmp size of 64M causes problems
by Red Hat Bugzilla 25 May '15

25 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216096 Bug ID: 1216096 Summary: Hard coded /tmp size of 64M causes problems Product: Fedora Version: 21 Component: docker-io Keywords: Extras Assignee: ichavero(a)redhat.com Reporter: agoldste(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, agoldste(a)redhat.com, eparis(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, lsu(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Depends On: 1215768 +++ This bug was initially created as a clone of Bug #1215768 +++ I'm looking at b482aff8fbb5dc59d25335b67353465071d6bd45 in rhatdan/docker It seems that you are hode coding all tmpfs mounts to 64M. Docker previously mounted tmpfs at /tmp and this added /run. Golang uses TMPDIR to do its builds. When doing a rather large build (like openshift) which is larger than 64M it obviously can not work! I think this size needs to be somehow configurable... Deciding that X is enough /tmp space for everyone just doesn't seem like a possibility... --- Additional comment from Daniel Walsh on 2015-04-28 08:13:12 EDT --- Eric, any chance of changing TMPDIR -> /var/tmp? --- Additional comment from Daniel Walsh on 2015-04-28 08:15:46 EDT --- This should also not be happening in a docker build? --- Additional comment from Daniel Walsh on 2015-04-28 08:32:57 EDT --- Removed the size restrictions on /tmp and /run Lokesh we need a new build of docker-1.6 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1215768 [Bug 1215768] Hard coded /tmp size of 64M causes problems -- You are receiving this mail because: You are on the CC list for the bug.

1 9

Broken dependencies: docker-io
by Fedora Koji Build System 23 May '15

23 May '15

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.

1 0

[Bug 1210447] New: patch to remove ECC p224 curve breaks existing software
by Red Hat Bugzilla 19 May '15

19 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1210447 Bug ID: 1210447 Summary: patch to remove ECC p224 curve breaks existing software Product: Fedora Version: 21 Component: golang Severity: high Assignee: vbatts(a)redhat.com Reporter: jeromyj(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: The patch to remove the p224 Elliptic curve from the go source tree breaks existing software. If a curve is believed to be insecure, please file a bug report against the go project and try to get it upstreamed. link to patch:http://koji.fedoraproject.org/koji/fileinfo?rpmID=6091693&filename=go… Version-Release number of selected component (if applicable): 21+ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1033604] New: Unable to start systemd service in Docker container
by Red Hat Bugzilla 19 May '15

19 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1033604 Bug ID: 1033604 Summary: Unable to start systemd service in 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: Using Dockerfile like this: FROM mattdm/fedora:latest RUN yum update -y RUN yum install -y redis RUN systemctl enable redis.service RUN systemctl start redis.service EXPOSE 6379 ENTRYPOINT ["/usr/bin/redis-cli"] The step 'systemctl start redis.service' failed with this error message: Failed to get D-Bus connection: No connection to service manager. 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. Save the above Dockerfile 2. Run: docker build -t test/redis . 3. The build fill faile on systemctl start. Actual results: The service failed to start due to D-BUS connection. Expected results: The service should be started? Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 33

Broken dependencies: docker-io
by Fedora Koji Build System 16 May '15

16 May '15

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.

1 0

[Bug 1213385] New: Docker 1.6 mounts /var/log/journal/4809557f6c5a83f899a25b507d72c4d5
by Red Hat Bugzilla 14 May '15

14 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1213385 Bug ID: 1213385 Summary: Docker 1.6 mounts /var/log/journal/4809557f6c5a83f899a25b507d72c4d5 Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: jpazdziora(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: With docker-io upgraded to 1.6, docker build and docker runs of https://github.com/adelton/docker-freeipa started to fail. The reason seems to be that the container gets /var/log/journal/{id-of-the-container?} mounted and you cannot get rid of it because [root@4809557f6c5a /]# umount -f /var/log/journal/4809557f6c5a83f899a25b507d72c4d5 umount: /var/log/journal/4809557f6c5a83f899a25b507d72c4d5: must be superuser to unmount That however prevents use from moving /var/log to VOLUME because in build time, /var/log/canot be removed: rm: cannot remove '/var/log/journal/cf00ac62f9dad464306c48f0267be479': Device or resource busy Version-Release number of selected component (if applicable): # rpm -q docker-io docker docker-io-1.6.0-1.git0591dce.fc21.x86_64 package docker is not installed How reproducible: Deterministic. Steps to Reproduce: 1. Install docker-io. 2. Make no changes to /etc/sysconfig/docker except adding --icc=false to OPTIONS. 3. Run the service. 4. Run docker run -ti fedora:20 mount | grep /var/log Actual results: /dev/mapper/fedora--server_mgmt12-root on /var/log/journal/4809557f6c5a83f899a25b507d72c4d5 type ext4 (rw,relatime,seclabel,data=ordered) Expected results: Nothing mounted on /var/log. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 23

Broken dependencies: docker-io
by Fedora Koji Build System 09 May '15

09 May '15

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.

1 0

[Bug 1032750] Review Request: golang-github-syndtr-gocapability - POSIX capability library for the Go programming language
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1032750 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|golang-github-syndtr-gocapa |golang-github-syndtr-gocapa |bility-0-0.9.git8e4cdcb.fc2 |bility-0-0.9.git8e4cdcb.el6 |0 | --- Comment #23 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-syndtr-gocapability-0-0.9.git8e4cdcb.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219058] CVE-2015-3629 docker: symlink traversal on container respawn allows local privilege escalation
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219058 Tomas Hoger <thoger(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tjay(a)redhat.com |security-response-team@redh | |at.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219061] CVE-2015-3627 docker: insecure opening of file-descriptor 1 leading to privilege escalation
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219061 Tomas Hoger <thoger(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tjay(a)redhat.com |security-response-team@redh | |at.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219063] CVE-2015-3630 docker: Read/write proc paths allow host modification & information disclosure
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219063 Tomas Hoger <thoger(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tjay(a)redhat.com |security-response-team@redh | |at.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219065] CVE-2015-3631 docker: volume mounts allow LSM profile escalation
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219065 Tomas Hoger <thoger(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tjay(a)redhat.com |security-response-team@redh | |at.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215912] New: docker-io-pkg-devel conflicts with docker-io-devel
by Red Hat Bugzilla 08 May '15

08 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1215912 Bug ID: 1215912 Summary: docker-io-pkg-devel conflicts with docker-io-devel Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: madko(a)linuxed.net QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: gocode source files from docker-io-pkg-devel are now in the docker-io-devel package. Therefor there are file conflicts. It's impossible now to upgrade or install if you have or want docker-io-devel and docker-io-pkg-devel. Version-Release number of selected component (if applicable): docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 docker-io-pkg-devel-1.5.0-1.fc21.x86_64 How reproducible: static Steps to Reproduce: 1. yum install docker-io-devel 2. yum install docker-io-pkg-devel Actual results: docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with files from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 especially files from /usr/share/gocode/src/github.com/docker/docker/pkg Expected results: may be docker-io-devel should obsolete docker-io-pkg-devel? Or no pkg go source files should be in the docker-io-devel? Additional info: docker-io-pkg-devel can be remove, not sure if we loose something. Extract from the yum error --- Transaction check error: file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/changes.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/archive.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/chrootarchive/archive.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/chrootarchive/archive_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/archive_unix.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/archive_windows.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/changes_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/archive/diff.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/broadcastwriter/broadcastwriter.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/devicemapper/devmapper.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/devicemapper/devmapper_wrapper.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/ioutils/readers.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/ioutils/readers_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/iptables/iptables.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/iptables/iptables_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/jsonlog/jsonlog.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/jsonlog/jsonlog_marshalling.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/jsonlog/jsonlog_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/mflag/flag.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/mount/sharedsubtree_linux_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/networkfs/resolvconf/resolvconf.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/parsers/filters/parse.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/parsers/parsers.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/parsers/parsers_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/reexec/reexec.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/sysinfo/sysinfo.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/lstat.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/lstat_windows.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/stat.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/stat_linux.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/stat_unsupported.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/system/stat_windows.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/term/term.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/term/term_windows.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/truncindex/truncindex.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 file /usr/share/gocode/src/github.com/docker/docker/pkg/truncindex/truncindex_test.go from install of docker-io-devel-1.6.0-2.git3eac457.fc21.x86_64 conflicts with file from package docker-io-pkg-devel-1.5.0-1.fc21.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219065] CVE-2015-3631 docker: volume mounts allow LSM profile escalation
by Red Hat Bugzilla 07 May '15

07 May '15

1 0

[Bug 1219063] CVE-2015-3630 docker: Read/write proc paths allow host modification & information disclosure
by Red Hat Bugzilla 07 May '15

07 May '15

1 0

[Bug 1219061] CVE-2015-3627 docker: insecure opening of file-descriptor 1 leading to privilege escalation
by Red Hat Bugzilla 07 May '15

07 May '15

1 0

[Bug 1219058] CVE-2015-3629 docker: symlink traversal on container respawn allows local privilege escalation
by Red Hat Bugzilla 07 May '15

07 May '15

1 0

[Bug 1219708] New: CVE-2015-3627 docker-io: docker: insecure opening of file-descriptor 1 leading to privilege escalation [epel-6]
by Red Hat Bugzilla 07 May '15

07 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219708 Bug ID: 1219708 Summary: CVE-2015-3627 docker-io: docker: insecure opening of file-descriptor 1 leading to privilege escalation [epel-6] Product: Fedora EPEL Version: el6 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219061 (CVE-2015-3627) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. epel-6 tracking bug for docker-io: see blocks bug list for full details of the security issue(s). This bug is never intended to be made public, please put any public notes in the blocked bugs. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219061 [Bug 1219061] CVE-2015-3627 docker: insecure opening of file-descriptor 1 leading to privilege escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219716] New: CVE-2015-3631 docker-io: docker: volume mounts allow LSM profile escalation [epel-6]
by Red Hat Bugzilla 07 May '15

07 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219716 Bug ID: 1219716 Summary: CVE-2015-3631 docker-io: docker: volume mounts allow LSM profile escalation [epel-6] Product: Fedora EPEL Version: el6 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219065 (CVE-2015-3631) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. epel-6 tracking bug for docker-io: see blocks bug list for full details of the security issue(s). This bug is never intended to be made public, please put any public notes in the blocked bugs. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219065 [Bug 1219065] CVE-2015-3631 docker: volume mounts allow LSM profile escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219712] New: CVE-2015-3630 docker-io: docker: Read/write proc paths allow host modification & information disclosure [epel-6]
by Red Hat Bugzilla 07 May '15

07 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219712 Bug ID: 1219712 Summary: CVE-2015-3630 docker-io: docker: Read/write proc paths allow host modification & information disclosure [epel-6] Product: Fedora EPEL Version: el6 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219063 (CVE-2015-3630) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. epel-6 tracking bug for docker-io: see blocks bug list for full details of the security issue(s). This bug is never intended to be made public, please put any public notes in the blocked bugs. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219063 [Bug 1219063] CVE-2015-3630 docker: Read/write proc paths allow host modification & information disclosure -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219704] New: CVE-2015-3629 docker-io: docker: symlink traversal on container respawn allows local privilege escalation [epel-6]
by Red Hat Bugzilla 07 May '15

07 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1219704 Bug ID: 1219704 Summary: CVE-2015-3629 docker-io: docker: symlink traversal on container respawn allows local privilege escalation [epel-6] Product: Fedora EPEL Version: el6 Component: docker-io Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: ichavero(a)redhat.com Reporter: tjay(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Blocks: 1219058 (CVE-2015-3629) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. epel-6 tracking bug for docker-io: see blocks bug list for full details of the security issue(s). This bug is never intended to be made public, please put any public notes in the blocked bugs. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1219058 [Bug 1219058] CVE-2015-3629 docker: symlink traversal on container respawn allows local privilege escalation -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1032750] Review Request: golang-github-syndtr-gocapability - POSIX capability library for the Go programming language
by Red Hat Bugzilla 04 May '15

04 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1032750 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|golang-github-syndtr-gocapa |golang-github-syndtr-gocapa |bility-0-0.9.git8e4cdcb.fc2 |bility-0-0.9.git8e4cdcb.fc2 |1 |0 --- Comment #22 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-syndtr-gocapability-0-0.9.git8e4cdcb.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209666] New: etcd-v2.0.9 is available
by Red Hat Bugzilla 04 May '15

04 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1209666 Bug ID: 1209666 Summary: etcd-v2.0.9 is available Product: Fedora Version: rawhide Component: etcd Keywords: FutureFeature, Triaged Assignee: lacypret(a)gmail.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, lacypret(a)gmail.com, lemenkov(a)gmail.com, lsm5(a)redhat.com, walters(a)redhat.com Latest upstream release: v2.0.9 Current version/release in rawhide: 2.0.8-0.1.fc23 URL: https://github.com/coreos/etcd 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.

1 8

[Bug 1032750] Review Request: golang-github-syndtr-gocapability - POSIX capability library for the Go programming language
by Red Hat Bugzilla 04 May '15

04 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1032750 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|golang-github-syndtr-gocapa |golang-github-syndtr-gocapa |bility-0-0.9.git8e4cdcb.fc2 |bility-0-0.9.git8e4cdcb.fc2 |2 |1 --- Comment #21 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-syndtr-gocapability-0-0.9.git8e4cdcb.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Broken dependencies: docker-io
by Fedora Koji Build System 02 May '15

02 May '15

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.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang May 2015