April 2015 - golang - Fedora mailing-lists

[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 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 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 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 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2015