June 2014 - golang - Fedora mailing-lists

[Bug 1100909] New: golang arm cross compile fails complaining about 5g
by Red Hat Bugzilla 13 Aug '14

13 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1100909 Bug ID: 1100909 Summary: golang arm cross compile fails complaining about 5g Product: Fedora Version: 20 Component: golang Severity: medium Assignee: vbatts(a)redhat.com Reporter: phil(a)sorber.net 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 Description of problem: After new 1.2.2-2 rpms for golang were updated, I attempted to cross compile a hello world for arm and it failed complaining about lack of 5g. Following packages installed: golang-1.2.2-2.fc20.x86_64 golang-pkg-bin-linux-amd64-1.2.2-2.fc20.x86_64 golang-pkg-linux-arm-1.2.2-2.fc20.noarch golang-src-1.2.2-2.fc20.noarch golang-pkg-linux-amd64-1.2.2-2.fc20.noarch $ GOOS=linux GOARCH=arm go build hello.go go tool: no such tool "5g" Version-Release number of selected component (if applicable): 1.2.2-2 How reproducible: Easy. Steps to Reproduce: 1. Install golang including the golang-pkg-linux-arm-1.2.2-2.fc20.noarch package 2. Attempt to build a hello world program with GOARCH=arm 3. Actual results: Error message: go tool: no such tool "5g" Expected results: A shiny new arm binary. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1101508] New: exec: "gcc": executable file not found in $PATH
by Red Hat Bugzilla 08 Aug '14

08 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1101508 Bug ID: 1101508 Summary: exec: "gcc": executable file not found in $PATH Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: mfojtik(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, s(a)shk.io, vbatts(a)redhat.com Description of problem: Running 'yum install gcc golang' fails with: Installing : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 50/252 # runtime/cgo exec: "gcc": executable file not found in $PATH warning: %post(golang-pkg-linux-amd64-1.2.2-7.fc20.noarch) scriptlet failed, exit status 2 Non-fatal POSTIN scriptlet failure in rpm package golang-pkg-linux-amd64-1.2.2-7.fc20.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1105901] New: golang-pkg-linux-amd64 is missing dependency on gcc
by Red Hat Bugzilla 08 Aug '14

08 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1105901 Bug ID: 1105901 Summary: golang-pkg-linux-amd64 is missing dependency on gcc Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: jumanjiman(a)gmail.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 Description of problem: On a fresh installation of Fedora 20 with golang-1.2.2-7.fc20.x86_64 or Fedora Rawhide with golang-1.3rc1-1.fc21.x86_64, go get errors out with: go install runtime/cgo: open /usr/lib/golang/pkg/linux_amd64/runtime/cgo.a: permission denied Version-Release number of selected component (if applicable): see above How reproducible: always. see https://github.com/jumanjiman/bz1099206 for a reproducer test harness based on docker with f20 and rawhide images. Steps to Reproduce: 1. build minimal f20 or rawhide system 2. install golang 3. observe error: Running transaction Installing : golang-src-1.2.2-7.fc20.noarch 1/52 Installing : golang-pkg-bin-linux-amd64-1.2.2-7.fc20.x86_64 2/52 Installing : golang-1.2.2-7.fc20.x86_64 3/52 Installing : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 4/52 # runtime/cgo exec: "gcc": executable file not found in $PATH warning: %post(golang-pkg-linux-amd64-1.2.2-7.fc20.noarch) scriptlet failed, exit status 2 Non-fatal POSTIN scriptlet failure in rpm package golang-pkg-linux-amd64-1.2.2-7.fc20.noarch Installing : mpfr-3.1.2-4.fc20.x86_64 5/52 Actual results: see above for rpm install error and `go get' error. Expected results: on fresh install, i should be able to run `go get' without error. Additional info: if you install gcc _before_ golang in separate yum commands, the above errors do not appear. See https://app.wercker.com/#applications/5394ce3e85147b684f0c91a4 for output of reproducer test harness. Note the "build images" and "run the test suite" sections. Potential related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1099206 https://bugzilla.redhat.com/show_bug.cgi?id=1099732 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1109039] New: finalize namespace errors with docker run
by Red Hat Bugzilla 25 Jul '14

25 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1109039 Bug ID: 1109039 Summary: finalize namespace errors with docker run Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lsm5(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: docker run will fail at times with namespace errors Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20 How reproducible: pretty much random from what I've noticed Steps to Reproduce: 1. docker run -it fedora bash 2. if you can't see the error in 1, run it again 3. repeat 2 until you see the error Actual results: Here's a sample from my machine: ------------------------------ lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:14 finalize namespace drop bounding set read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:18 finalize namespace drop capabilities read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash bash-4.3# exit exit lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:25 finalize namespace drop bounding set read /proc/1/status: bad file descriptor ------------------------------- Expected results: container shell should be accessible everytime -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1109533] New: finalize namespace errors with docker run
by Red Hat Bugzilla 25 Jul '14

25 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1109533 Bug ID: 1109533 Summary: finalize namespace errors with docker run Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, agrimm(a)redhat.com, fullung(a)gmail.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 Depends On: 1109039 +++ This bug was initially created as a clone of Bug #1109039 +++ Description of problem: docker run will fail at times with namespace errors Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20 How reproducible: pretty much random from what I've noticed Steps to Reproduce: 1. docker run -it fedora bash 2. if you can't see the error in 1, run it again 3. repeat 2 until you see the error Actual results: Here's a sample from my machine: ------------------------------ lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:14 finalize namespace drop bounding set read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:18 finalize namespace drop capabilities read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash bash-4.3# exit exit lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:25 finalize namespace drop bounding set read /proc/1/status: bad file descriptor ------------------------------- Expected results: container shell should be accessible everytime --- Additional comment from Lokesh Mandvekar on 2014-06-13 03:24:28 EDT --- Hmm, I can't seem to be able to replicate this on my rawhide machine, no matter how many times I try this, regardless of the image (centos,fedora,debian,ubuntu) --- Additional comment from Vincent Batts on 2014-06-13 14:43:54 EDT --- using a newer version of gocapability (3c85049eae) fixes this for me, on RHEL6 https://github.com/dotcloud/docker/commit/4bf03a0fac48a06298afa149d43392457… --- Additional comment from Andy Grimm on 2014-06-13 15:18:38 EDT --- I confirmed that switching from f20 docker-io to rawhide docker-io fixed it for me. --- Additional comment from Fedora Update System on 2014-06-13 16:19:20 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-13 16:45:54 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-13 16:53:05 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-14 16:00:27 EDT --- Package golang-github-syndtr-gocapability-0-0.7.git3c85049.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing golang-github-syndtr-gocapability-0-0.7.git3c85049.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1647/golang-github… then log in and leave karma (feedback). Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1109039 [Bug 1109039] finalize namespace errors with docker run -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1112700] New: docker container not started, bad file descriptor
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1112700 Bug ID: 1112700 Summary: docker container not started, bad file descriptor 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 Created attachment 911745 --> https://bugzilla.redhat.com/attachment.cgi?id=911745&action=edit /var/log/messages output Description of problem: Sometimes when I try to start container I get this message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor and the container is not started. Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: rarely Steps to Reproduce: 1. use `docker run ...` (in this example: `/usr/bin/docker -D run --interactive --tty --name test_eHmi localhost:5000/ldoktor/fedora:latest bash -c bash` Actual results: Container is not started, message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor is in the container output. Expected results: Container should start. Additional info: There were around 14 containers running and 2 not running when this bug occurred. This bug happened to me 3 or 4 times during one week (testing docker, so the failure percentage is really low). -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1112748] New: Selinux prevents docker-io from updating /etc/passwd within a container
by Red Hat Bugzilla 22 Jul '14

22 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1112748 Bug ID: 1112748 Summary: Selinux prevents docker-io from updating /etc/passwd within a container Product: Fedora Version: 20 Component: docker-io Severity: high Assignee: lsm5(a)redhat.com Reporter: artaxerxes2(a)iname.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: Running a certain docker command fails to run the container as expected since selinux intercept a call to update /etc/passwd within the container. Version-Release number of selected component (if applicable): Docker version 1.0.0, build 63fe64c/1.0.0 selinux policy version is 29 How reproducible: always Steps to Reproduce: 1. # yum upgrade 2. # yum install docker-io 3. add username to the docker group and restart the daemon 4. verify 'getenforce' returns 'Enforcing' 5. docker run -t -i -p 80:80 -p 20022:22 oskarhane/docker-wordpress-nginx-ssh Actual results: 140624 15:34:46 mysqld_safe Logging to syslog. 140624 15:34:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysql root password: Yohraequ2eiB wordpress password: ieHie5toi0zo ssh password: se2Gai9eengu usermod: failure while writing changes to /etc/passwd % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 58606 100 58606 0 0 60339 0 --:--:-- --:--:-- --:--:-- 62148 Archive: nginx-helper.1.8.1.zip nginx-helper.1.8.1 packaged creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/readme.txt creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/admin.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/install.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-sidebar.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-general.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-support.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/config.json creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.eot inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.svg inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.ttf inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.woff creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/nginx-fontello.css inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx.js inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/rtp-social-icons-32-32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/logo.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/style.css extracting: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-icon-32x32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/nginx-helper.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/compatibility.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.mo inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.po inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/purger.php % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 38126 100 38126 0 0 151k 0 --:--:-- --:--:-- --:--:-- 154k Archive: wp-ffpc.1.5.0.zip wp-ffpc.1.5.0 packaged creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-acache.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-class.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-nginx-sample.conf inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/uninstall.php creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-admin.css inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-abstract.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-utilities.php sed: warning: failed to set default file creation context to system_u:object_r:svirt_sandbox_file_t:s0:c8,c525: Permission deniedStarting memcached: memcached. 140624 15:34:59 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended /usr/local/lib/python2.7/dist-packages/supervisor-3.0-py2.7.egg/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2014-06-24 15:35:00,547 CRIT Supervisor running as root (no user in config file) 2014-06-24 15:35:00,646 INFO RPC interface 'supervisor' initialized 2014-06-24 15:35:00,646 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-06-24 15:35:00,646 INFO supervisord started with pid 380 2014-06-24 15:35:01,648 INFO spawned: 'nginx' with pid 391 2014-06-24 15:35:01,650 INFO spawned: 'mysqld' with pid 392 2014-06-24 15:35:01,651 INFO spawned: 'php5-fpm' with pid 393 2014-06-24 15:35:01,652 INFO spawned: 'ssh' with pid 394 2014-06-24 15:35:02,756 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: ssh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Expected results: 140624 15:36:48 mysqld_safe Logging to syslog. 140624 15:36:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysql root password: Eehujoh3ooyo wordpress password: nana8aiTh6ju ssh password: Eengoo2liMie % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 58606 100 58606 0 0 38969 0 0:00:01 0:00:01 --:--:-- 39412 Archive: nginx-helper.1.8.1.zip nginx-helper.1.8.1 packaged creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/install.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-general.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-sidebar.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-support.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/logo.png extracting: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-icon-32x32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/rtp-social-icons-32-32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx.js inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/style.css creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.ttf inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.woff inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.svg inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.eot creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/nginx-fontello.css inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/config.json inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/admin.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/nginx-helper.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/compatibility.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.mo inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.po inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/purger.php % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 38126 100 38126 0 0 49638 0 --:--:-- --:--:-- --:--:-- 49903 Archive: wp-ffpc.1.5.0.zip wp-ffpc.1.5.0 packaged creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-nginx-sample.conf inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-class.php creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-admin.css inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-abstract.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-utilities.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/uninstall.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-acache.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php Starting memcached: memcached. /usr/local/lib/python2.7/dist-packages/supervisor-3.0-py2.7.egg/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2014-06-24 15:37:02,595 CRIT Supervisor running as root (no user in config file) 2014-06-24 15:37:02,603 INFO RPC interface 'supervisor' initialized 2014-06-24 15:37:02,603 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-06-24 15:37:02,603 INFO supervisord started with pid 385 140624 15:37:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 2014-06-24 15:37:03,606 INFO spawned: 'nginx' with pid 396 2014-06-24 15:37:03,607 INFO spawned: 'mysqld' with pid 397 2014-06-24 15:37:03,608 INFO spawned: 'php5-fpm' with pid 398 2014-06-24 15:37:03,609 INFO spawned: 'ssh' with pid 399 2014-06-24 15:37:04,716 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: ssh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Additional info: If selinux is set to non-enforcing (setenforce 0), then the problem disappears. Looking at the audit.log file there is nothing related to failed update around the time of the usermod command is launched. I tried the exact same steps on CentOS 6.5 and had no issue at all, even in Enforcing mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1101654] New: Permission denied when running Fedora images on Ubuntu
by Red Hat Bugzilla 14 Jul '14

14 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1101654 Bug ID: 1101654 Summary: Permission denied when running Fedora images on Ubuntu Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: sthorger(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 899597 --> https://bugzilla.redhat.com/attachment.cgi?id=899597&action=edit Example Dockerfile Description of problem: Trying to run a basic Docker image from Fedora on Ubuntu 14.04, gives the following error message: 2014/05/27 17:00:26 exec: "/usr/bin/echo": stat /usr/bin/echo: permission denied Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Build attach Dockerfile 2. Run Actual results: 2014/05/27 17:00:26 exec: "/usr/bin/echo": stat /usr/bin/echo: permission denied Expected results: Hello world! Additional info: Removing "User hello" or "RUN yum -y update" makes it work as expected -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1110497] New: go test fails for multiple golang-* libraries
by Red Hat Bugzilla 08 Jul '14

08 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1110497 Bug ID: 1110497 Summary: go test fails for multiple golang-* libraries Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: lsm5(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 Description of problem: apparently, ever since the upgrade to go1.3rc2, go test in %check fails. Here's a sample from golang-github-gorilla-mux: go test github.com/gorilla/mux /var/tmp/rpm-tmp.iEoDQJ: line 31: 10812 Segmentation fault GOPATH=/usr/share/gocode:/home/lsm5/repositories/pkgs/fedora/golang-github-gorilla-mux/BUILDROOT/golang-github-gorilla-mux-0-0.14.git136d54f.fc21.x86_64//usr/share/gocode go test github.com/gorilla/mux error: Bad exit status from /var/tmp/rpm-tmp.iEoDQJ (%check) Version-Release number of selected component (if applicable): 1.3rc2-1.fc21 How reproducible: always Steps to Reproduce: 1. install latest golang on rawhide 2. try rebuilding any previously built golang lib (golang-github-gorilla-context or golang-github-gorilla-mux for instance) 3. see error -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1105046] New: argument prototype mismatch spew on update
by Red Hat Bugzilla 08 Jul '14

08 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1105046 Bug ID: 1105046 Summary: argument prototype mismatch spew on update Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: yaneti(a)declera.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 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1096076] New: ADDing file to symlinked /bin hangs, docker process spinning at 100 % CPU
by Red Hat Bugzilla 25 Jun '14

25 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1096076 Bug ID: 1096076 Summary: ADDing file to symlinked /bin hangs, docker process spinning at 100 % CPU Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jpazdziora(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 Fedora 20, /bin is a symlink to usr/bin. When Dockerfile tries to ADD file to /bin, the process will hang, with the daemon spinning at 100 % CPU. Version-Release number of selected component (if applicable): docker-io-0.11.1-1.fc20.x86_64 Seen on 0.10* as well. How reproducible: Deterministic. Steps to Reproduce: 1. echo test > testfile 2. have Dockerfile with FROM fedora:20 ADD testfile /bin/testfile 3. run docker build -t test-symlink . Actual results: Uploading context 4.608 kB Uploading context Step 0 : FROM fedora:20 ---> b7de3133ff98 Step 1 : ADD testfile /bin/testfile and that's it, top in another terminal shows Expected results: # docker build -t test-symlink . Uploading context 5.632 kB Uploading context Step 0 : FROM fedora:20 ---> b7de3133ff98 Step 1 : ADD testfile /bin/testfile ---> 6fb52b6363f7 Removing intermediate container 11254a256eb7 Successfully built 6fb52b6363f7 # Additional info: ADD to /usr/bin/testfile works. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1105789] New: docker-io-0.12.0 is available
by Red Hat Bugzilla 24 Jun '14

24 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1105789 Bug ID: 1105789 Summary: docker-io-0.12.0 is available Product: Fedora Version: rawhide Component: docker-io Keywords: FutureFeature, Triaged Assignee: lsm5(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org 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 Latest upstream release: 0.12.0 Current version/release in Fedora Rawhide: 0.11.1-11.fc21 URL: https://github.com/dotcloud/docker/releases 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 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1094664] New: docker-io-0.10.0-2 disables access to /dev/shm
by Red Hat Bugzilla 24 Jun '14

24 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1094664 Bug ID: 1094664 Summary: docker-io-0.10.0-2 disables access to /dev/shm Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jpazdziora(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 testing FreeIPA server and the 389 server in Docker container, I started to see errors like Failed to create semaphore for stats file/Permission denied with docker-io from updates-testing. Upon closer look, /dev/shm seems to be mounted with 1755, which is different from what docker-io 0.9.1 does and what you get on bare metal. Version-Release number of selected component (if applicable): docker-io-0.10.0-2.fc20.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. docker run -ti fedora:20 /bin/bash 2. In the container shell, run mount | grep /dev/shm ls -la /dev/shm exit 3. Downgrade to docker-io-0.9.1 and repeat. Actual results: # docker run -ti fedora:20 /bin/bash bash-4.2# mount | grep /dev/shm shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,size=65536k,mode=1755) # docker run -ti fedora:20 /bin/bash bash-4.2# ls -la /dev/shm total 4 drwxrwxrwt. 2 root root 40 May 6 08:06 . drwxr-xr-x. 4 root root 4096 May 6 08:06 .. bash-4.2# exit # rpm -q docker-io docker-io-0.9.1-1.fc20.x86_64 # yum downgrade docker-io -y [...] # rpm -q docker-io docker-io-0.9.1-1.fc20.x86_64 # docker run -ti fedora:20 /bin/bash bash-4.2# mount | grep /dev/shm shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,size=65536k) bash-4.2# ls -la /dev/shm total 4 drwxrwxrwt. 2 root root 40 May 6 09:16 . drwxr-xr-x. 4 root root 4096 May 6 09:16 .. bash-4.2# exit exit # Expected results: Permissions on /dev/shm the same as on docker-io-0.9.1. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1096123] New: useradd within EL6 container fails: failure while writing changes to /etc/passwd
by Red Hat Bugzilla 24 Jun '14

24 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1096123 Bug ID: 1096123 Summary: useradd within EL6 container fails: failure while writing changes to /etc/passwd Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: dcleal(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: Between docker-io-0.10.0-2.fc20 and docker-io-0.11.1-1.fc20, the following has started failing: $ docker run -t centos /usr/sbin/useradd test useradd: failure while writing changes to /etc/passwd 'centos' is the official CentOS 6 image (0b443ba03958). The Fedora 20 host has SELinux enforcing, and the same issue occurs when set to permissive. No AVCs are seen. Version-Release number of selected component (if applicable): docker-io-0.11.1-1.fc20.x86_64 kernel-3.14.2-200.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. docker pull centos 2. docker run -t centos /usr/sbin/useradd test Actual results: useradd: failure while writing changes to /etc/passwd Expected results: no output Additional info: On 0.10.0, an strace of useradd shows: open("/etc/group", O_RDONLY|O_CLOEXEC) = 11 fstat(11, {st_mode=S_IFREG|0644, st_size=379, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7feb5efe5000 read(11, "root:x:0:\nbin:x:1:bin,daemon\ndae"..., 4096) = 379 close(11) = 0 munmap(0x7feb5efe5000, 4096) = 0 fchown(10, 500, 12) = 0 fchmod(10, 0660) = 0 fsync(10) = 0 close(10) = 0 fstat(6, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0 gettid() = 14 open("/proc/self/task/14/attr/fscreate", O_RDONLY) = 10 read(10, "", 4095) = 0 close(10) = 0 gettid() = 14 open("/proc/self/task/14/attr/fscreate", O_RDWR) = 10 write(10, "system_u:object_r:file_t:s0\0", 28) = 28 close(10) = 0 fstat(6, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0 umask(077) = 022 open("/etc/passwd-", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 10 umask(022) = 077 lseek(6, 0, SEEK_SET) = 0 read(6, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 670 fstat(10, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7feb5efe5000 read(6, "", 4096) = 0 write(10, "root:x:0:0:root:/root:/bin/bash\n"..., 670) = 670 While on 0.11.1, strace shows: open("/etc/group", O_RDONLY|O_CLOEXEC) = 10 fstat(10, {st_mode=S_IFREG|0644, st_size=379, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2905a38000 read(10, "root:x:0:\nbin:x:1:bin,daemon\ndae"..., 4096) = 379 close(10) = 0 munmap(0x7f2905a38000, 4096) = 0 fchown(9, 500, 12) = 0 fchmod(9, 0660) = 0 fsync(9) = 0 close(9) = 0 fstat(5, {st_mode=S_IFREG|0644, st_size=675, ...}) = 0 gettid() = 30 open("/proc/self/task/30/attr/fscreate", O_RDONLY) = 9 read(9, "", 4095) = 0 close(9) = 0 gettid() = 30 open("/proc/self/task/30/attr/fscreate", O_RDWR) = -1 EROFS (Read-only file system) write(2, "useradd: failure while writing c"..., 54useradd: failure while writing changes to /etc/passwd ) = 54 -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1103595] New: Docker daemon uses 100 % CPU
by Red Hat Bugzilla 23 Jun '14

23 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1103595 Bug ID: 1103595 Summary: Docker daemon uses 100 % CPU Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jpazdziora(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 run docker build which downloads images. While this happens, the docker daemon is using up-to 100 % CPU when it probably does not have that much work to do, given the speed of my network. Version-Release number of selected component (if applicable): # rpm -qf /usr/bin/docker docker-io-0.11.1-7.fc20.x86_64 How reproducible: Seen once. Steps to Reproduce: 1. ( echo FROM fedora:20 ; ADD testfile /bin/testfile ) > Dockerfile 2. docker build -t test-1 . 3. In other terminal, observe top while the images are being downloaded. Actual results: # docker build -t test-1 . Uploading context 3.584 kB Uploading context Step 0 : FROM fedora:20 Pulling repository fedora 4f4eba4c47b8: Downloading [===========================================> ] 101.4 MB/115.9 MB 5s 511136ea3c5a: Download complete 8c982ec5ea99: Download complete and while the download is running # top top - 03:26:45 up 6 days, 36 min, 2 users, load average: 0.58, 0.30, 0.17 Tasks: 153 total, 2 running, 151 sleeping, 0 stopped, 0 zombie %Cpu(s): 14.8 us, 11.3 sy, 0.0 ni, 43.9 id, 27.1 wa, 1.8 hi, 1.1 si, 0.0 st KiB Mem: 8160392 total, 4357084 used, 3803308 free, 176932 buffers KiB Swap: 8273916 total, 0 used, 8273916 free, 3490916 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 16112 root 20 0 588820 35144 7144 S 97.3 0.4 1:31.79 docker 16119 root 0 -20 0 0 0 S 3.6 0.0 0:04.29 loop0 and # ps axuw | grep docker root 16112 7.6 0.4 588820 36176 ? Ssl 03:05 1:37 /usr/bin/docker -d --selinux-enabled root 16287 0.3 0.0 284764 5308 pts/0 Sl+ 03:26 0:00 docker build -t test-1 . root 16341 0.0 0.0 112668 964 pts/1 S+ 03:26 0:00 grep --color=auto docker Expected results: I'd expect the daemon not consuming 100 % CPU when the only action happening is download of images on fairly slow line. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1103323] New: docker on RHEL6.5 no longer needs to default to lxc
by Red Hat Bugzilla 18 Jun '14

18 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1103323 Bug ID: 1103323 Summary: docker on RHEL6.5 no longer needs to default to lxc Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vbatts(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: docker daemon on RHEL6 (and centos) is patched to launch with 'lxc' execdriver, instead of the docker 'native' libcontainer Version-Release number of selected component (if applicable): $ docker version Client version: 0.11.1 Client API version: 1.11 Go version (client): go1.2.1 Git commit (client): fb99f99/0.11.1 Server version: 0.11.1 Server API version: 1.11 Git commit (server): fb99f99/0.11.1 Go version (server): go1.2.1 Last stable version: 0.11.1 The reason we had mad this switch was due to the network bridge setup for libcontainer had not worked correctly at first. This has since been fixed upstream. $ docker run -it fedora ping -c1 google.com PING google.com (173.194.121.1) 56(84) bytes of data. 64 bytes from iad23s25-in-f1.1e100.net (173.194.121.1): icmp_seq=1 ttl=45 time=16.2 ms --- google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 16.294/16.294/16.294/0.000 ms -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1087546] New: Request epel7 branch
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1087546 Bug ID: 1087546 Summary: Request epel7 branch Product: Fedora EPEL Version: epel7 Component: golang-github-coreos-go-systemd Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: bobbypowers(a)gmail.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com Package Change Request ====================== Package Name: golang-github-coreos-go-systemd New Branches: epel7 Owners: lsm5 InitialCC: golang-sig -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1072041] New: Include a -devel that provides the docker source
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1072041 Bug ID: 1072041 Summary: Include a -devel that provides the docker source Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vbatts(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 For client tooling, that uses internal packages of docker, the docker source needs to available as a library. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1099984] Pam issue when trying to login to a container running sshd.
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1099984 Daniel Walsh <dwalsh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|docker-io |pam Assignee|lsm5(a)redhat.com |tmraz(a)redhat.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1102019] New: cannot remove /var/lib/docker just after a fresh install even when docker is stopped
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1102019 Bug ID: 1102019 Summary: cannot remove /var/lib/docker just after a fresh install even when docker is stopped Product: Fedora EPEL Version: el6 Component: docker-io Severity: medium Priority: medium Assignee: lsm5(a)redhat.com Reporter: vdasgupt(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: Cannot remove /var/lib/docker just after a fresh install even when docker is stopped. And even though the docker runtime root has been changed to /home/docker and is no longer /var/lib/docker # rmdir /var/lib/docker rmdir: failed to remove `/var/lib/docker': Device or resource busy lsof does not show anyone using this file/dir Version-Release number of selected component (if applicable): RHEL 6 Kernel 2.6.32-431.el6 Docker version 0.11.1, build fb99f99/0.11.1 Steps to Reproduce: 1. yum -y docker-io 2. service docker start ; service docker stop 3. add -g="/home/docker" to other_args in /etc/sysconfig/docker 4. service docker start ; service docker stop 5. checked that the docker runtime env files are now in /home/docker 6. Try to remove or rename /var/lib/docker and it does not allow Actual results: rmdir: failed to remove `/var/lib/docker': Device or resource busy Expected results: Should have removed or allowed to rename the directory -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1106155] New: docker-io: FTBFS in rawhide
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1106155 Bug ID: 1106155 Summary: docker-io: FTBFS in rawhide Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: dennis(a)ausil.us 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 Blocks: 1105908 Your package docker-io failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=6952304 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1105908 [Bug 1105908] Fedora 21 Mass Rebuild FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1108970] New: libtinfo.so.5: cannot open shared object file: No such file or directory
by Red Hat Bugzilla 17 Jun '14

17 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1108970 Bug ID: 1108970 Summary: libtinfo.so.5: cannot open shared object file: No such file or directory Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: taim(a)bosboot.org 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: Docker errors out with "/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory" Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: For me, every time. Steps to Reproduce: 1. $ sudo docker run ubuntu /bin/bash Actual results: /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Expected results: /bin/bash runs and returns 0. Additional info: $ journalctl -u docker Jun 12 22:43:38 localhost.localdomain docker[935]: 2014/06/12 22:43:38 POST /v1.12/containers/create Jun 12 22:43:38 localhost.localdomain docker[935]: [7ab53ddb] +job create() Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job create() = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: 2014/06/12 22:43:39 POST /v1.12/containers/309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a/attach?stderr=1&s Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job container_inspect(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job container_inspect(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job attach(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: 2014/06/12 22:43:39 POST /v1.12/containers/309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a/start Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job start(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job allocate_interface(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job allocate_interface(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job start(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job release_interface(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job release_interface(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job attach(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) Jun 12 22:43:39 localhost.localdomain docker[935]: 2014/06/12 22:43:39 POST /v1.12/containers/309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a/wait Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] +job wait(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) Jun 12 22:43:39 localhost.localdomain docker[935]: [7ab53ddb] -job wait(309a11feeaa52c13d06b5da6e36dd5bcd0adeff0659a8130cbe016d6b4e0b84a) = OK (0) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1098120] New: Unable to buid an run an image using sshd.
by Red Hat Bugzilla 13 Jun '14

13 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1098120 Bug ID: 1098120 Summary: Unable to buid an run an image using sshd. Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: pantinor(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: Unable to succesfully build and run a fairly simple image that used to work. Version-Release number of selected component (if applicable): $ docker -v Docker version 0.11.1, build fb99f99/0.11.1 How reproducible: Always Steps to Reproduce: mkdir docker_test cd docker_test wget http://pastebin.com/raw.php?i=ie8BRcC4 -O Dockerfile docker build -t sshd --no-cache Actual results: $ docker build -t sshd --no-cache . Uploading context 2.56 kB Uploading context Step 0 : FROM centos ---> 539c0211cd76 Step 1 : RUN yum install -y openssh-server ---> Running in 65f28c081323 Loaded plugins: fastestmirror Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package openssh-server.x86_64 0:5.3p1-94.el6 will be installed --> Processing Dependency: openssh = 5.3p1-94.el6 for package: openssh-server-5.3p1-94.el6.x86_64 --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package: openssh-server-5.3p1-94.el6.x86_64 --> Processing Dependency: libcrypto.so.10(OPENSSL_1.0.1)(64bit) for package: openssh-server-5.3p1-94.el6.x86_64 --> Processing Dependency: libwrap.so.0()(64bit) for package: openssh-server-5.3p1-94.el6.x86_64 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-server-5.3p1-94.el6.x86_64 --> Running transaction check ---> Package fipscheck-lib.x86_64 0:1.2.0-7.el6 will be installed --> Processing Dependency: /usr/bin/fipscheck for package: fipscheck-lib-1.2.0-7.el6.x86_64 ---> Package openssh.x86_64 0:5.3p1-94.el6 will be installed ---> Package openssl.x86_64 0:1.0.0-27.el6_4.2 will be updated ---> Package openssl.x86_64 0:1.0.1e-16.el6_5.7 will be an update --> Processing Dependency: make for package: openssl-1.0.1e-16.el6_5.7.x86_64 ---> Package tcp_wrappers-libs.x86_64 0:7.6-57.el6 will be installed --> Running transaction check ---> Package fipscheck.x86_64 0:1.2.0-7.el6 will be installed ---> Package make.x86_64 1:3.81-20.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: openssh-server x86_64 5.3p1-94.el6 base 311 k Installing for dependencies: fipscheck x86_64 1.2.0-7.el6 base 14 k fipscheck-lib x86_64 1.2.0-7.el6 base 8.3 k make x86_64 1:3.81-20.el6 base 389 k openssh x86_64 5.3p1-94.el6 base 258 k tcp_wrappers-libs x86_64 7.6-57.el6 base 62 k Updating for dependencies: openssl x86_64 1.0.1e-16.el6_5.7 updates 1.5 M Transaction Summary ================================================================================ Install 6 Package(s) Upgrade 1 Package(s) Total download size: 2.5 M Downloading Packages: -------------------------------------------------------------------------------- Total 569 kB/s | 2.5 MB 00:04 warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 Importing GPG key 0xC105B9DE: Userid : CentOS-6 Key (CentOS 6 Official Signing Key) <centos-6-key(a)centos.org> Package: centos-release-6-4.el6.centos.10.x86_64 (@febootstrap/$releasever) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : tcp_wrappers-libs-7.6-57.el6.x86_64 1/8 Installing : 1:make-3.81-20.el6.x86_64 2/8 Updating : openssl-1.0.1e-16.el6_5.7.x86_64 3/8 Installing : fipscheck-lib-1.2.0-7.el6.x86_64 4/8 Installing : fipscheck-1.2.0-7.el6.x86_64 5/8 Installing : openssh-5.3p1-94.el6.x86_64 6/8 Installing : openssh-server-5.3p1-94.el6.x86_64 7/8 groupadd: failure while writing changes to /etc/group Cleanup : openssl-1.0.0-27.el6_4.2.x86_64 8/8 Verifying : 1:make-3.81-20.el6.x86_64 1/8 Verifying : tcp_wrappers-libs-7.6-57.el6.x86_64 2/8 Verifying : fipscheck-1.2.0-7.el6.x86_64 3/8 Verifying : openssl-1.0.1e-16.el6_5.7.x86_64 4/8 Verifying : openssh-5.3p1-94.el6.x86_64 5/8 Verifying : openssh-server-5.3p1-94.el6.x86_64 6/8 Verifying : fipscheck-lib-1.2.0-7.el6.x86_64 7/8 Verifying : openssl-1.0.0-27.el6_4.2.x86_64 8/8 Installed: openssh-server.x86_64 0:5.3p1-94.el6 Dependency Installed: fipscheck.x86_64 0:1.2.0-7.el6 fipscheck-lib.x86_64 0:1.2.0-7.el6 make.x86_64 1:3.81-20.el6 openssh.x86_64 0:5.3p1-94.el6 tcp_wrappers-libs.x86_64 0:7.6-57.el6 Dependency Updated: openssl.x86_64 0:1.0.1e-16.el6_5.7 Complete! ---> e869dfd88b15 Removing intermediate container 65f28c081323 Step 2 : RUN sed -i 's/#PermitEmptyPasswords no/PermitEmptyPasswords yes/;s/#UseDNS yes/UseDNS no/' /etc/ssh/sshd_config ---> Running in 8673e7861c41 sed: warning: failed to set default file creation context to system_u:object_r:file_t:s0: Read-only file system ---> f49ebe0bc026 Removing intermediate container 8673e7861c41 Step 3 : CMD service sshd start ; bash ---> Running in b4db6af6261e ---> b9d7e3852943 Removing intermediate container b4db6af6261e Successfully built b9d7e3852943 Expected results: A build and run with no errors. Everything works as expected when run for instance in a boot2docker vm: https://github.com/boot2docker/boot2docker/releases/download/v0.9.1/boot2do… Additional info: $ getenforce Permissive The error is recent. I am not sure if the problem is Docker, selinux, or Centos base files, but the full operation used to succed without any problem in past. Note sed warning: sed: warning: failed to set default file creation context to system_u:object_r:file_t:s0: Read-only file system ---> f49ebe0bc026 When running a container from that image, the ssh fails: $ docker run -t -i sshd Generating SSH1 RSA host key: No such file or directory [ OK ] Generating SSH2 RSA host key: No such file or directory [ OK ] Generating SSH2 DSA host key: No such file or directory [ OK ] Starting sshd: Privilege separation user sshd does not exist [FAILED] bash-4.1# exit -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1096849] New: docker daemon for epel7 doesn't allow for additional options
by Red Hat Bugzilla 11 Jun '14

11 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1096849 Bug ID: 1096849 Summary: docker daemon for epel7 doesn't allow for additional options Product: Fedora EPEL Version: epel7 Component: docker-io Severity: medium Assignee: lsm5(a)redhat.com Reporter: jperrin(a)centos.org 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: For el6, epel's docker build creates /etc/sysconfig/docker, which allows other options to be passed to the docker daemon. the systemd unit files for epel7's docker build do not. Version-Release number of selected component (if applicable): docker-io-0.10.0-2.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. yum install docker-io 2. less /usr/lib/systemd/system/docker.service Actual results: There is no $other_args defined in the systemd unit file, nor is there an /etc/sysconfig/docker in which to define the options. Expected results: Same as the el6 docker. You should be able to pass additional arguments for bridging, dns, or restart options Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1084232] New: Docker fails to pull images from behind a proxy server
by Red Hat Bugzilla 09 Jun '14

09 Jun '14

https://bugzilla.redhat.com/show_bug.cgi?id=1084232 Bug ID: 1084232 Summary: Docker fails to pull images from behind a proxy server Product: Fedora Version: 20 Component: docker-io Severity: low Assignee: lsm5(a)redhat.com Reporter: dbond(a)nrggos.com.au 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: Docker-io does not work behind a proxy server The docker daemon does not use the proxy and attempts to access directly Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: HTTP_PROXY=http://my_proxy:3128/ docker pull busybox Actual results: Pulling repository busybox 2014/04/04 08:56:42 Get https://index.docker.io/v1/repositories/busybox/images: dial tcp: lookup index.docker.io on [10.x.x.x]:53: no such host Expected results: Unable to find image 'busybox' locally Pulling repository busybox 769b9341d937: Download complete 511136ea3c5a: Download complete bf747efa0e2f: Download complete 48e5f45168b9: Download complete hello world Additional info: Fixed by adding an environment file to docker.service Add file /etc/sysconfig/docker containing HTTP_PROXY=http://my_proxy:3128 Add EnvironmentFile=-/etc/sysconfig/docker to docker.service file -- You are receiving this mail because: You are on the CC list for the bug.

1 13

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang June 2014