April 2015 - golang - Fedora mailing-lists

[Bug 1085881] Review Request: golang-github-spf13-cobra - A Commander for modern go CLI interactions
by Red Hat Bugzilla 20 Apr '15

20 Apr '15

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

1 0

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 19 Apr '15

19 Apr '15

golang-github-google-gofuzz has broken dependencies in the epel-6 tree: On ppc64: golang-github-google-gofuzz-devel-0-0.5.gitbbcb9da.el6.noarch requires golang >= 0:1.2.1-3 Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 19 Apr '15

19 Apr '15

golang-github-google-gofuzz has broken dependencies in the epel-6 tree: On ppc64: golang-github-google-gofuzz-devel-0-0.5.gitbbcb9da.el6.noarch requires golang >= 0:1.2.1-3 Please resolve this as soon as possible.

1 0

[Bug 1191438] New: docker-io-1.5.0 is available
by Red Hat Bugzilla 17 Apr '15

17 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1191438 Bug ID: 1191438 Summary: docker-io-1.5.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: 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 Latest upstream release: 1.5.0 Current version/release in Fedora Rawhide: 1.4.1-27.git76baa35.fc22 URL: https://github.com/docker/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 Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1060502] Review Request: golang-github-mitchellh-cli - A library for implementing powerful command-line interfaces in Go
by Red Hat Bugzilla 16 Apr '15

16 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1060502 Jan Chaloupka <jchaloup(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1212318 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1212318 [Bug 1212318] Review Request: golang-github-hashicorp-serf- Service orchestration and management tool http://www.serfdom.io -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #7 from smahajan(a)redhat.com <smahajan(a)redhat.com> --- Issue exists on fedora 21 docker. Docker version: Client version: 1.5.0 Client API version: 1.17 but it's fixed in upstream 1.6.0 which will be released this Friday. Shishir -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #6 from Daniel Walsh <dwalsh(a)redhat.com> --- Fixed in docker-1.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 smahajan(a)redhat.com <smahajan(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED --- Comment #5 from smahajan(a)redhat.com <smahajan(a)redhat.com> --- This one is fixed in upstream. After the `--until` timestamp, `docker events` command will die. Changing it to modified. Shishir -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1046717] New: Cancel run or pull operation doesn't actually stop the ongoing task
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1046717 Bug ID: 1046717 Summary: Cancel run or pull operation doesn't actually stop the ongoing task Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: lsm5(a)redhat.com Reporter: baptiste.millemathias(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: I've downloaded a docker image using "docker pull bradrydzewski/mongodb:2.4" and when I wanted to run it I did a "docker run bradrydzewski/mongodb" as the image name was named like that, and I saw docker pulling another image (the size was different), so I hit Ctrl+C thinking to going kill the operation. However a ps fax showed me dockerd was still downloading something, certainly image bradrydzewski/mongodb Version-Release number of selected component (if applicable): docker-io-0.7.0-14.fc20.x86_64 How reproducible: 100 % Steps to Reproduce: 1. docker pull bradrydzewski/mongodb:2.4 (let the complete operation happens) 2. docker run bradrydzewski/mongodb, and hit ctrl+c after few seconds Actual results: Dockerd still download image Expected results: docker client should ask Dockerd to cancel the download of the image -- You are receiving this mail because: You are on the CC list for the bug.

1 9

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087704 Bug ID: 1087704 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Fedora Version: 20 Component: docker-io Severity: low Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1087720] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087720 Bug ID: 1087720 Summary: signal 27 (SIGPROF) not passed to container using --sig-proxy Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: When I send signal 27 to the docker process, which is running with --sig-proxy=true, it's not forwarded. Other signals are... Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -27 $PID Actual results: nothing Expected results: Received 27, ignoring... Additional info: When you send any other signal (apart from 19 or 9) it works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 Daniel Walsh <dwalsh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|unspecified |low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #4 from Daniel Walsh <dwalsh(a)redhat.com> --- shishir can you check if this one is fixed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171928] update from 3.2-27 to 3.2-28 fails on docker fedora 21 image
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

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

1 0

[Bug 1166312] New: etcd unit should support command line options
by Red Hat Bugzilla 13 Apr '15

13 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1166312 Bug ID: 1166312 Summary: etcd unit should support command line options Product: Fedora Version: 21 Component: etcd Assignee: lacypret(a)gmail.com Reporter: lars(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lacypret(a)gmail.com, lemenkov(a)gmail.com The "etcd.service" unit distributed with Fedora 21 (atomic) does not contain any facilities for passing arguments to etcd. That is, it looks like this: [Service] Type=simple StandardOutput=null WorkingDirectory=/var/lib/etcd User=etcd ExecStart=/usr/bin/etcd This means that if a deployer wants to pass arguments to etcd at boot (such as a discovery URL), the only option is to introduce a new unit file in /etc/systemd/system. This works, but it seems like a heavy hammer. It seems as if a better choice would be to introduce an EnvironmentFile directive like we do for so many other units. Something like: [Service] Type=simple StandardOutput=null WorkingDirectory=/var/lib/etcd User=etcd EnvironmentFile=/etc/sysconfig/etcd ExecStart=/usr/bin/etcd $OPTIONS -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1166950] New: Unable to run "mysql" docker image on Fedora atomic due to selinux
by Red Hat Bugzilla 13 Apr '15

13 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1166950 Bug ID: 1166950 Summary: Unable to run "mysql" docker image on Fedora atomic due to selinux Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)fedoraproject.org Reporter: lars(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, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com The "mysql" Docker image creates a volume on /var/lib/mysql inside the container. At runtime, the entrypoint script attempts to chown this directory to the mysql user, which leads to the following error: # docker run -e MYSQL_ROOT_PASSWORD=secret mysql FATAL ERROR: Could not chown directory /var/lib/mysql And the following AVC: type=AVC msg=audit(1416629737.562:201): avc: denied { setattr } for pid=22615 comm="mysql_install_d" name="d27cb6010a47942d7dc4826ebfe138ea62888fc9a5dedcaf14ebb3a1f45781c2" dev="dm-0" ino=6329484 scontext=system_u:system_r:svirt_lxc_net_t:s0:c190,c586 tcontext=system_u:object_r:docker_var_lib_t:s0 tclass=dir permissive=0 Which translates to: module docker 1.0; require { type svirt_lxc_net_t; type docker_var_lib_t; class dir setattr; } #============= svirt_lxc_net_t ============== allow svirt_lxc_net_t docker_var_lib_t:dir setattr; A simple reproducer is to create a Dockerfile with the following: FROM fedora VOLUME /var/lib/myvolume RUN chown nobody /var/lib/myvolume And attempt to "docker build .": Sending build context to Docker daemon 2.56 kB Sending build context to Docker daemon Step 0 : FROM fedora ---> 7d3f07f8de5f Step 1 : VOLUME /var/lib/myvolume ---> Running in 5f2e6a9a51e0 ---> ea49c8d042b2 Removing intermediate container 5f2e6a9a51e0 Step 2 : RUN chown nobody /var/lib/myvolume ---> Running in d1083d0ccc68 chown: changing ownership of '/var/lib/myvolume': Permission denied 2014/11/22 04:27:19 The command [/bin/sh -c chown nobody /var/lib/myvolume] returned a non-zero code: 1 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 12 Apr '15

12 Apr '15

golang-github-google-gofuzz has broken dependencies in the epel-6 tree: On ppc64: golang-github-google-gofuzz-devel-0-0.5.gitbbcb9da.el6.noarch requires golang >= 0:1.2.1-3 Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 12 Apr '15

12 Apr '15

golang-github-google-gofuzz has broken dependencies in the epel-6 tree: On ppc64: golang-github-google-gofuzz-devel-0-0.5.gitbbcb9da.el6.noarch requires golang >= 0:1.2.1-3 Please resolve this as soon as possible.

1 0

[Bug 1085881] Review Request: golang-github-spf13-cobra - A Commander for modern go CLI interactions
by Red Hat Bugzilla 11 Apr '15

11 Apr '15

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

1 0

[Bug 1082734] Review Request: golang-github-godbus-dbus - Go client bindings for D-Bus
by Red Hat Bugzilla 11 Apr '15

11 Apr '15

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

1 0

[Bug 1082734] Review Request: golang-github-godbus-dbus - Go client bindings for D-Bus
by Red Hat Bugzilla 10 Apr '15

10 Apr '15

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

1 0

[Bug 1085881] Review Request: golang-github-spf13-cobra - A Commander for modern go CLI interactions
by Red Hat Bugzilla 10 Apr '15

10 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1085881 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|golang-github-spf13-cobra-0 |golang-github-spf13-cobra-0 |-0.6.gitf8e1ec5.el6 |-0.7.git79bd93d.fc21 --- Comment #30 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-spf13-cobra-0-0.7.git79bd93d.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210472] New: too many open files
by Red Hat Bugzilla 09 Apr '15

09 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1210472 Bug ID: 1210472 Summary: too many open files Product: Fedora EPEL Version: epel7 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: briemers(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: After awhile of running docker commands, particularly as part of a "watch" statement, I state to get too many pipe2 errors. Version-Release number of selected component (if applicable): How reproducible: Unknown. This has happened to me 3 times so far. Steps to Reproduce: 1. Run a docker command in a watch loop, such as: watch -n 30 docker run -t -i --rm fedora date 2. 3. Actual results: Eventually one starts to see output like: time="2015-04-09T15:25:25-04:00" level="fatal" msg="Post http:///var/run/docker.sock/v1.16/containers/3543b03f71195ca4522e794e7e0d83d8642b59ceb140d30a9d7fcef760424893/start: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?" If I control-C, run "docker rm $(docker ps -q -a)" there are many instances to clean-up. Afterwards, if I try running a new docker command without the watch part I get the error: FATA[0000] Error response from daemon: Cannot start container 6252aa7de7f1217f654d1551c56e9d544eb9a588446996e0ae473458b2bf1251: pipe2: too many open files Expected results: Should just keep working. Additional info: The command I'm actually using is an sqlplus script, but I thought an example with date might be much easier to use to reproduce with. Doing a "service docker restart" resolves the issue, but it also aborts all my running docker containers... -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1210444] New: asdf
by Red Hat Bugzilla 09 Apr '15

09 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1210444 Bug ID: 1210444 Summary: asdf Product: Fedora Version: 21 Component: golang Assignee: vbatts(a)redhat.com Reporter: striker(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: 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 1

[Bug 1195804] New: docker run fails on rawhide with setenforce 1
by Red Hat Bugzilla 09 Apr '15

09 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1195804 Bug ID: 1195804 Summary: docker run fails on rawhide with setenforce 1 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: 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: On rawhide, docker run commands fail with selinux enforcing. Feb 24 09:34:01 naruto kernel: [605832.428983] audit: type=1400 audit(1424792041.549:3572): avc: denied { entrypoint } for pid=19015 comm="docker" path="/var/lib/docker/init/dockerinit-1.5.0-dev" dev="sda2" ino=134594 scontext=system_u:system_r:spc_t:s0 tcontext=system_u:object_r:docker_var_lib_t:s0 tclass=file permissive=0 Feb 24 09:34:01 naruto kernel: [605832.429083] audit: type=1300 audit(1424792041.549:3572): arch=c000003e syscall=59 success=no exit=-13 a0=c208b05290 a1=c208602500 a2=c2085ceb20 a3=0 items=0 ppid=7465 pid=19015 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="docker" exe="/usr/bin/docker" subj=system_u:system_r:docker_t:s0 key=(null) Feb 24 09:34:01 naruto kernel: [605832.429110] audit: type=1327 audit(1424792041.549:3572): proctitle=2F7573722F62696E2F646F636B6572002D64002D2D73656C696E75782D656E61626C6564 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2015