https://bugzilla.redhat.com/show_bug.cgi?id=1096123
Sean Summers <seansummers(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seansummers(a)gmail.com
--- Comment #27 from Sean Summers <seansummers(a)gmail.com> ---
I am able to start containers that were running before upgrade/reboot, but
running any new ones fails.
After a reboot, with any new containers:
$ cat /etc/redhat-release
Fedora release 20 (Heisenbug)
$ rpm -qa | grep docker
python-docker-py-0.2.3-8.fc20.x86_64
fedora-dockerfiles-0-0.5.git122ef5d.fc20.noarch
docker-io-0.11.1-7.fc20.x86_64
$ mount | grep docker
/dev/sda3 on /var/lib/docker type btrfs (rw,relatime,seclabel,space_cache)
$ docker run -i -t fedora:latest /bin/bash
/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open
shared object file: Permission denied
$ docker run -i -t centos:latest /bin/bash
/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open
shared object file: No such file or directory
$ docker run -i -t ubuntu:latest /bin/bash
/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open
shared object file: No such file or directory
$ sudo grep docker /var/log/yum.log*
/var/log/yum.log-20140611:Feb 18 17:09:32 Installed:
docker-io-0.7.6-4.fc20.x86_64
/var/log/yum.log-20140611:Feb 24 13:40:04 Updated:
docker-io-0.8.0-3.fc20.x86_64
/var/log/yum.log-20140611:Mar 10 14:00:24 Updated:
docker-io-0.8.1-1.fc20.x86_64
/var/log/yum.log-20140611:Mar 31 13:03:26 Updated:
docker-io-0.9.0-3.fc20.x86_64
/var/log/yum.log-20140611:Apr 17 11:52:07 Updated:
docker-io-0.9.1-1.fc20.x86_64
/var/log/yum.log-20140611:May 12 15:27:54 Updated:
docker-io-0.11.1-1.fc20.x86_64
/var/log/yum.log-20140611:Jun 02 10:40:46 Installed:
python-docker-py-0.2.3-8.fc20.x86_64
/var/log/yum.log-20140611:Jun 02 10:43:25 Installed:
fedora-dockerfiles-0-0.5.git122ef5d.fc20.noarch
/var/log/yum.log-20140611:Jun 10 07:25:17 Updated:
docker-io-0.11.1-7.fc20.x86_64
$
--
You are receiving this mail because:
You are on the CC list for the bug.