[Bug 1192742] New: Fix DWARF for variable references
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1192742
Bug ID: 1192742
Summary: Fix DWARF for variable references
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 991800
--> https://bugzilla.redhat.com/attachment.cgi?id=991800&action=edit
A bit hacky fix
Description of problem:
https://sourceware.org/gdb/wiki/GoDebugging#golang_Wrong_DW_TAG_variable
golang provides &name variable names and the DWARF interface uses one more
pointer than in the source.
Version-Release number of selected component (if applicable):
golang-1.4.1-1.fc22.x86_64
How reproducible:
Always.
Steps to Reproduce:
-------------------
package main
func main () {
var i int
ip:=&i
ipp:=&ip
go func() {
**ipp++
}()
}
-------------------
Actual results:
(gdb) b 8
(gdb) r
(gdb) p i
No symbol "i" in current context.
(gdb) p &i
No symbol "i" in current context.
(gdb) p '&i'
Invalid character constant.
(gdb) p ' &i'
$1 = (int *) 0xc20800a080
(gdb) p *' &i'
$2 = 0
(gdb) p ' &ip'
$3 = (int **) 0xc20803a000
(gdb) p *' &ip'
$4 = (int *) 0xc20800a080
(gdb) p **' &ip'
$5 = 0
(gdb) p ' &ipp'
$6 = (int ***) 0xc20803a008
(gdb) p *' &ipp'
$7 = (int **) 0xc20803a000
(gdb) p **' &ipp'
$8 = (int *) 0xc20800a080
(gdb) p ***' &ipp'
$9 = 0
Expected results:
(gdb) b 8
(gdb) r
(gdb) p i
$1 = (int &) @0xc20800a080: 0
(gdb) p ip
$2 = (int *&) @0xc20803a000: 0xc20800a080
(gdb) p *ip
$3 = 0
(gdb) p ipp
$4 = (int **&) @0xc20803a008: 0xc20803a000
(gdb) p *ipp
$5 = (int *) 0xc20800a080
(gdb) p **ipp
$6 = 0
(gdb) whatis i
type = int &
(gdb) whatis ip
type = int *&
(gdb) whatis ipp
type = int **&
Additional info:
But you said golang upstream is writing some new linker so maybe this hack is
not much relevant for upstream. DW_AT_name of the reference types is IMO
incorrect but I do not think it matters much for GDB; for 'ipp' with this patch
there is:
<fe78> DW_AT_name : &(***int)
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 1 month
[Bug 1186669] New: Failed to start Docker Application Container Engine.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1186669
Bug ID: 1186669
Summary: Failed to start Docker Application Container Engine.
Product: Fedora
Version: 21
Component: docker-io
Severity: high
Assignee: lsm5(a)redhat.com
Reporter: bugzilla.redhat.com(a)trancecode.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Created attachment 985059
--> https://bugzilla.redhat.com/attachment.cgi?id=985059&action=edit
grep -i 'docker' /var/log/audit/audit.log | tail
Description of problem:
I yum-updated to F21 latest and now docker service fails to start on boot.
This update included reboot to new kernel 3.18
[root@vm117 ~]# uname -a
Linux vm117 3.18.3-201.fc21.x86_64 #1 SMP Mon Jan 19 15:59:31 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
Maybe this could be related to the other new warning that I see in
joutnalctl -b
SELinux is preventing sm-notify from write access on the file nlm_end_grace.
For complete SELinux messages. run sealert
and
Dependency failed for Network Manager Wait Online.
Which I assume is new with 3.18 since web search found this:
https://www.kernel.org/pub/linux/utils/nfs-utils/1.3.1/1.3.1-Changelog
I don't see anything notable in /var/log/messages
Will attach a grep of /var/log/audit/audit.log
Version-Release number of selected component (if applicable):
[root@vm117 ~]# yum info docker-io.x86_64
Loaded plugins: langpacks
Installed Packages
Name : docker-io
Arch : x86_64
Version : 1.4.1
Release : 5.fc21
Size : 19 M
Repo : installed
>From repo : updates
How reproducible:
100% Service Fails to start on every boot.
Steps to Reproduce:
1. Reboot Fedora
2. systemctl status docker.service
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 1 month
[Bug 1165615] New: Docker needs at least device-mapper-libs-1.02.90-1 to start correcty as a systemd service
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1165615
Bug ID: 1165615
Summary: Docker needs at least device-mapper-libs-1.02.90-1 to
start correcty as a systemd service
Product: Fedora
Version: 21
Component: docker-io
Severity: low
Priority: low
Assignee: lsm5(a)fedoraproject.org
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Description of problem:
After installing docker on clean installation of F21, systemctl start docker
fails.
Version-Release number of selected component (if applicable):
docker-io-1.3.1-2.fc21.x86_64
device-mapper-libs-1.02.88-2.fc21.x86_64
How reproducible:
Always
Steps to Reproduce:
1. install F21
2. yum install docker
3. systemctl start docker
Actual results:
docker does not start
Expected results:
docker starts
Additional info:
I don't update the system (no yum update), because I don't want to increase
system's size in virtual machine. Thus device-mapper-libs does not get updated
to the latest build.
# systemctl start docker
Job for docker.service failed. See 'systemctl status docker.service' and
'journalctl -xn' for details.
# status docker.service -l
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
Active: failed (Result: exit-code) since Wed 2014-11-19 06:04:42 EST; 1min
16s ago
Docs: http://docs.docker.com
Process: 2473 ExecStart=/usr/bin/docker -d -H fd:// $OPTIONS
$DOCKER_STORAGE_OPTIONS (code=exited, status=127)
Main PID: 2473 (code=exited, status=127)
Nov 19 06:04:42 localhost.localdomain docker[2473]: 2014/11/19 06:04:42 docker
daemon: 1.3.1 4e9bbfa/1.3.1; xecdriver: native; graphdriver:
Nov 19 06:04:42 localhost.localdomain docker[2473]: [54d8ccdb] +job
serveapi(fd://)
Nov 19 06:04:42 localhost.localdomain docker[2473]: [info] Listening for HTTP
on fd ()
Nov 19 06:04:42 localhost.localdomain docker[2473]: /usr/bin/docker: relocation
error: /usr/bin/docker: symbol dm_task_get_info_with_deferred_remove, version
Base not defined in file libdevmapper.so.1.02 with link time reference
Nov 19 06:04:42 localhost.localdomain systemd[1]: docker.service: main process
exited, code=exited, status=127/n/a
Nov 19 06:04:42 localhost.localdomain systemd[1]: Failed to start Docker
Application Container Engine.
Nov 19 06:04:42 localhost.localdomain systemd[1]: Unit docker.service entered
failed state.
Among others:
/usr/bin/docker: relocation error: /usr/bin/docker: symbol
dm_task_get_info_with_deferred_remove, version Base not defined in file
libdevmapper.so.1.02 with link time reference
Update of device-mapper-libs to device-mapper-libs-1.02.90-1 solves the
problem.
Proposing to add device-mapper-libs >= 1.02.90-1 to spec file.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 1 month
[Bug 1173950] New: docker-io can't be installed on rhel 6.5 due to requirement device-mapper-libs >= 1.02.90-1
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1173950
Bug ID: 1173950
Summary: docker-io can't be installed on rhel 6.5 due to
requirement device-mapper-libs >= 1.02.90-1
Product: Fedora EPEL
Version: el6
Component: docker-io
Severity: high
Assignee: lsm5(a)redhat.com
Reporter: abonas(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:
docker-io.x86_64 0:1.3.2-2.el6 can't be installed on rhel 6.5 due to
requirement device-mapper-libs >= 1.02.90-1:
How reproducible:
Steps to Reproduce: (on rhel 6.5)
1. sudo yum install docker-io
2. device-mapper-libs can't be upgraded to the requested version.
3.
Actual results:
error:
Running transaction check
---> Package docker-io.x86_64 0:1.3.2-2.el6 will be installed
--> Processing Dependency: device-mapper-libs >= 1.02.90-1 for package:
docker-io-1.3.2-2.el6.x86_64
--> Finished Dependency Resolution
Error: Package: docker-io-1.3.2-2.el6.x86_64 (epel)
Requires: device-mapper-libs >= 1.02.90-1
Installed: device-mapper-libs-1.02.79-8.el6.x86_64
(@production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.79-8.el6
Available: device-mapper-libs-1.02.53-8.el6.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.53-8.el6
Available: device-mapper-libs-1.02.53-8.el6_0.2.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.53-8.el6_0.2
Available: device-mapper-libs-1.02.53-8.el6_0.3.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.53-8.el6_0.3
Available: device-mapper-libs-1.02.53-8.el6_0.4.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.53-8.el6_0.4
Available: device-mapper-libs-1.02.62-3.el6.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.62-3.el6
Available: device-mapper-libs-1.02.66-6.el6.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.66-6.el6
Available: device-mapper-libs-1.02.74-10.el6.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.74-10.el6
Available: device-mapper-libs-1.02.74-10.el6_3.2.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.74-10.el6_3.2
Available: device-mapper-libs-1.02.74-10.el6_3.3.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.74-10.el6_3.3
Available: device-mapper-libs-1.02.77-9.el6.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.77-9.el6
Available: device-mapper-libs-1.02.77-9.el6_4.2.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.77-9.el6_4.2
Available: device-mapper-libs-1.02.77-9.el6_4.3.i686
(production-rhel-x86_64-workstation-6.5)
device-mapper-libs = 1.02.77-9.el6_4.3
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 1 month
[Bug 1195328] New: docker master branch build fails on rawhide and f21
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1195328
Bug ID: 1195328
Summary: docker master branch build fails on rawhide and f21
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 and f21, I see this with the latest commit on master
(7d2188f9955d3f2002ff8c2e566ef84121de5217) ... haven't yet tracked down where
exactly this got introduced. 1.5.0 release builds just fine though.
---> Making bundle: dynbinary (in bundles/1.5.0-dev/dynbinary)
Created binary:
/home/lsm5/repositories/github.com/docker/docker/bundles/1.5.0-dev/dynbinary/dockerinit-1.5.0-dev
# _/home/lsm5/repositories/github.com/docker/docker/docker
/usr/bin/ld: cannot find -lsqlite3
/usr/bin/ld: cannot find -ldevmapper
/var/tmp/go-link-lP6Xfs/000008.o: In function `mygetpwuid_r':
/usr/lib/golang/src/pkg/os/user/lookup_unix.go:72: warning: Using 'getpwnam_r'
in statically linked applications requires at runtime the shared libraries from
the glibc version used for linking
/var/tmp/go-link-lP6Xfs/000008.o: In function
`_cgo_0db69e1b5445_Cfunc_mygetpwuid_r':
/usr/lib/golang/src/pkg/os/user/lookup_unix.go:27: warning: Using 'getpwuid_r'
in statically linked applications requires at runtime the shared libraries from
the glibc version used for linking
/var/tmp/go-link-lP6Xfs/000000.o: In function
`_cgo_14616c423265_Cfunc_freeaddrinfo':
/usr/lib/golang/src/pkg/net/cgo_unix.go:53: warning: Using 'getaddrinfo' in
statically linked applications requires at runtime the shared libraries from
the glibc version used for linking
collect2: error: ld returned 1 exit status
/usr/lib/golang/pkg/tool/linux_amd64/6l: running gcc failed: unsuccessful exit
status 0x100
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1166082] New: Fedora 21 Atomic Image: docker service is not starting during boot as it is not enabled by-default
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1166082
Bug ID: 1166082
Summary: Fedora 21 Atomic Image: docker service is not starting
during boot as it is not enabled by-default
Product: Atomic
Component: docker-io
Severity: medium
Assignee: alexl(a)redhat.com
Reporter: lmohanty(a)redhat.com
CC: admiller(a)redhat.com, extras-qa(a)fedoraproject.org,
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
Depends On: 1166076
+++ This bug was initially created as a clone of Bug #1166076 +++
Description of problem:
Docker service is not starting during boot of Atomic image of Fedora 21 as it
is not enabled in systemd.
bash-4.3# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
Active: active (running) since Thu 2014-11-20 10:43:03 UTC; 47min ago
Docs: http://docs.docker.com
Main PID: 907 (docker)
CGroup: /system.slice/docker.service
└─907 /usr/bin/docker -d -H fd:// --selinux-enabled --storage-opt
dm.fs=xfs --storage-opt dm.datadev=/dev/atomicos/docker-data --storage...
Version-Release number of selected component (if applicable):
Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2
How reproducible:
Always
Steps to Reproduce:
1. use Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2 to boot.
2. check if docker service is running
3.
Actual results:
Expected results:
Additional info:
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1166076
[Bug 1166076] Fedora 21 Atomic Image: docker service is not starting during
boot as it is not enabled by-default
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1166918] New: Docker exec causes Error response from daemon: Unsupported: Exec is not supported by the lxc driver
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1166918
Bug ID: 1166918
Summary: Docker exec causes Error response from daemon:
Unsupported: Exec is not supported by the lxc driver
Product: Fedora EPEL
Version: el6
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: jltronson(a)directv.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
Description of problem:
When I attempt to run Docker exec on a running container I get the following
error:
Error response from daemon: Unsupported: Exec is not supported by the lxc
driver
Version-Release number of selected component (if applicable):
# uname -a
Linux 2.6.32-504.el6.x86_64 #1 SMP Tue Oct 14 01:47:47 PDT 2014 x86_64 x86_64
x86_64 GNU/Linux
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)
# docker version
Client version: 1.3.1
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 4e9bbfa
OS/Arch (client): linux/amd64
Server version: 1.3.1
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): 4e9bbfa
How reproducible: 100%
Steps to Reproduce:
1. $ docker exec -it my_docker_image bash
Actual results:
Error response from daemon: Unsupported: Exec is not supported by the lxc
driver
Expected results:
The expected result is that I get a bash prompt.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1182596] New: AVC denials when running docker build
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1182596
Bug ID: 1182596
Summary: AVC denials when running docker build
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: pkamenickova(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:
Sometimes when running docker build, these AVC denials appear:
type=AVC msg=audit(1421329727.232:1403): avc: denied { name_connect } for
pid=14266 comm="yum" dest=21 scontext=system_u:system_r:docker_t:s0
tcontext=system_u:object_r:ftp_port_t:s0 tclass=tcp_socket permissive=1
type=AVC msg=audit(1421329730.463:1404): avc: denied { name_connect } for
pid=14266 comm="yum" dest=55226 scontext=system_u:system_r:docker_t:s0
tcontext=system_u:object_r:ephemeral_port_t:s0 tclass=tcp_socket permissive=1
type=AVC msg=audit(1421329735.658:1405): avc: denied { name_connect } for
pid=14327 comm="urlgrabber-ext-" dest=63179
scontext=system_u:system_r:docker_t:s0
tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket permissive=1
Note: Because we are not sure what is correct behaviour of this, I have opened
it as docker-io issue, not selinux.
Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-103.fc21.noarch
docker-io-1.4.1-4.fc21.x86_64
How reproducible:
Force yum to use some ftp repository, use RUN yum install command in Dockerfile
Example: RUN yum install --enablerepo=fedoraftp -y zsh
Run docker build
Steps to Reproduce:
1. yum install --enablerepo=updates-testing -y docker-io
2. service docker start
3. fedoraftp.repo:
[fedoraftp]
name=fedoraftp
baseurl=ftp://ftp.linux.cz/pub/linux/fedora/linux/releases/20/Everything/x86_64/os/
gpgcheck=0
enabled=1
4. Dockerfile:
FROM fedora:20
ADD fedoraftp.repo /etc/yum.repos.d/fedoraftp.repo
RUN yum install --disablerepo='*' --enablerepo=fedoraftp -y zsh
5. docker build -t example .
Actual results:
Expected results:
No AVC denial
Additional info:
Output of sesearch on Fedora21:
sesearch --allow -s docker_t -t ftp_port_t
Found 6 semantic av rules:
allow docker_t port_type : tcp_socket name_bind ;
allow docker_t port_type : udp_socket { recv_msg send_msg name_bind } ;
allow nsswitch_domain port_type : tcp_socket { recv_msg send_msg } ;
allow nsswitch_domain port_type : udp_socket { recv_msg send_msg } ;
allow docker_t port_type : tcp_socket { recv_msg send_msg name_connect } ;
allow nsswitch_domain reserved_port_type : tcp_socket name_connect ;
I've tried to reproduce this issue on Fedora 20
(selinux-policy-3.12.1-196.fc20.noarch) and RHEL 7
(selinux-policy-3.12.1-153.el7.noarch) - it seems these versions of selinux
already have the rules for this kind of thing (maybe ??).
Fedora20 sesearch:
sesearch --allow -s docker_t -t ftp_port_t
Found 10 semantic av rules:
allow corenet_unconfined_type port_type : tcp_socket { recv_msg send_msg
name_bind name_connect } ;
allow corenet_unconfined_type port_type : udp_socket { recv_msg send_msg
name_bind } ;
allow corenet_unconfined_type port_type : rawip_socket name_bind ;
allow corenet_unconfined_type port_type : dccp_socket { recv_msg send_msg
name_bind name_connect } ;
allow docker_t port_type : tcp_socket name_bind ;
allow docker_t port_type : udp_socket { recv_msg send_msg name_bind } ;
allow nsswitch_domain port_type : tcp_socket { recv_msg send_msg } ;
allow nsswitch_domain port_type : udp_socket { recv_msg send_msg } ;
allow nsswitch_domain reserved_port_type : tcp_socket name_connect ;
allow docker_t port_type : tcp_socket { recv_msg send_msg name_connect } ;
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1192567] New: Docker Build Hangs
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1192567
Bug ID: 1192567
Summary: Docker Build Hangs
Product: Fedora EPEL
Version: el6
Component: docker-io
Severity: urgent
Assignee: lsm5(a)redhat.com
Reporter: me2blr(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:
We are trying to build docker image. It was working fine on Docker version
1.2.0, build fa7b24f/1.2.0. But up gradation to latest 1.4 it's started
hangs.We were unable to build images anymore.
Version-Release number of selected component (if applicable):
$ sudo docker -v
Docker version 1.4.1, build 5bc2ff8/1.4.1
$ sudo docker info
Containers: 2
Images: 110
Storage Driver: devicemapper
Pool Name: docker-8:17-2228225-pool
Pool Blocksize: 65.54 kB
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 12.64 GB
Data Space Total: 107.4 GB
Metadata Space Used: 15.24 MB
Metadata Space Total: 2.147 GB
Library Version: 1.02.89-RHEL6 (2014-09-01)
Execution Driver: native-0.2
Kernel Version: 2.6.32-431.29.2.el6.x86_64
Operating System: <unknown>
CPUs: 1
Total Memory: 1.833 GiB
How reproducible:
Install docker using following steps
1) Run wget
http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm or
wget "http://epel.mirror.srv.co.ge/6/i386/epel-release-6-8.noarch.rpm"
2) Run sudo rpm -Uvh epel-release-6*.rpm
3) Run sudo yum -y install docker-io
4) Run sudo service docker start
5) cd /etc/yum.repos.d
6) sudo wget public-yum.oracle.com/public-yum-ol6.repo
7) sudo wget public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 -O
/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
8) sudo yum update device-mapper
9) sudo service docker restart
Any Dockerfile can be used to reproduce issue.
FROM ubuntu
# Install vnc, xvfb in order to create a 'fake' display and firefox
RUN ls
EXPOSE 5900
CMD ["uname"]
Steps to Reproduce:
1. Install docker-io as mentioned above
2. use above dockerfile or any then run docker build -t "sample" --rm=true .
3. 90% it hangs node, session will be lost.
Actual results:
hangs node, session will be lost.
Expected results:
Should build images
Additional info:
Tried sudo yum update as mentioned in the below site. But still problem remains
same
https://docs.docker.com/installation/rhel/
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1194686] New: docker run looks for dockerinit in /var/lib/docker
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1194686
Bug ID: 1194686
Summary: docker run looks for dockerinit in /var/lib/docker
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
Version-Release number of selected component (if applicable):
docker-io-1.5.0-9.git09b785f.fc23.x86_64
How reproducible:
always
Steps to Reproduce:
1. yum install docker
2. systemctl start docker
3. sudo docker run -it fedora bash
Actual results:
$ sudo docker run -it fedora bash
FATA[0002] Error response from daemon: Cannot start container
fbbe6f117cc7bf2545f530c62eb4b43b8b9dc485ce340f1b6473cd4fbc346f5f: fork/exec
/var/lib/docker/init/dockerinit-1.5.0-dev: permission denied
Expected results:
container shell
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months