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.
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=1128041https://github.com/docker/docker/issues/7952
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1219534
Bug ID: 1219534
Summary: Getting docker daemon not running error
Product: Fedora EPEL
Version: epel7
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: ramesh.reddy(a)bankofamerica.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem: Getting docker daemon not running error
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Installed EPEL on 6.5 RHEL
2. Installed docker-io
3. Able to run "docker" command
4. When running "docker run -i -t fedora /bin/bash" command using without root,
getting below error
FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix
/var/run/docker.sock
<http:///var/run/docker.sock/v1.17/containers/create:%20dial%20unix%20/var/run/docker.sock>
: permission denied. Are you trying to connect to a TLS-enabled daemon without
TLS?
However, with root getting diff error like below for the same command
FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this
host?
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1218599
Bug ID: 1218599
Summary: docker can no longer copy from inside the container
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Created attachment 1022155
--> https://bugzilla.redhat.com/attachment.cgi?id=1022155&action=edit
dockerfile reproducer
Description of problem:
After upgrading docker I can no longer cp from inside a container. I upgraded
to docker-io-1.6.0-4.git350a636.fc21.x86_64 and tried
docker-io-1.6.0-4.git350a636.fc21.x86_64 as well. Both fail.
This is a regression in F21. That worked fine with 1.3.2
How reproducible:
Outside the container use:
docker cp my_container:/tmp/file-created-in-the-container ./tmp/
FATA[0000] Error response from daemon: Could not find the file ...
Using ssh I can verify that the files exist
Steps to Reproduce:
0. Copy the attached dockerfile into docker-dir
1. sudo docker build -t test-image docker-dir
2. sudo docker run -P --privileged=true --name xxx-name test-image
3. sudo docker cp xxx-name:/tmp/xxx /tmp/
Actual results:
With 1.3.2: nothing. The file is copied.
With 1.6.0:
FATA[0000] Error response from daemon: Could not find the file /tmp/xxx in
container xxx-name
Expected results:
The file should have been copied.
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
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.
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.
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.
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.