[Bug 1166076] 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=1166076
Bug ID: 1166076
Summary: Fedora 21 Atomic Image: docker service is not starting
during boot as it is not enabled by-default
Product: Fedora
Version: 21
Component: docker-io
Severity: medium
Assignee: lsm5(a)fedoraproject.org
Reporter: lmohanty(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
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:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1101123] New: docker package binary conflicts with docker-io
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1101123
Bug ID: 1101123
Summary: docker package binary conflicts with docker-io
Product: Fedora
Version: 20
Component: docker-io
Severity: medium
Assignee: lsm5(a)redhat.com
Reporter: dmcf(a)dcorking.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, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
There is a file name conflict for /usr/bin/docker between 2 Fedora 20 packages.
Version-Release number of selected component (if applicable):
docker-1.5-10.fc20.x86_64 (f20 updates, a dockapp that provides a system tray
for WindowMaker, XFCE etc.)
docker-io-0.11.1-1.fc20.x86_64.rpm (f20 updates, a new Linux containerization
app that has proven very popular)
How reproducible: Consistent.
Steps to Reproduce:
1. sudo yum install docker
2. sudo yum install docker-io
Actual results:
Transaction check error:
file /usr/bin/docker from install of docker-io-0.11.1-1.fc20.x86_64 conflicts
with file from package docker-1.5-10.fc20.x86_64
Expected results:
All packages in F20 should be able to co-exist unless a conflict is documented
in the RPM file.
Since the conflict is only file naming, one of these packages could be patched
to allow it to co-exist with the other.
Additional info:
Possible workaround that keeps docker working for me follows.
(It allows docker-io to install, but I am not sure if docker-io is fully
functioning.)
#!/bin/bash
sudo mv /usr/bin/docker /usr/bin/wmdocker
# user must change dock icons that link to docker to point to wmdocker
sudo yum install docker-io --downloadonly
cd /var/cache/yum/x86_64/20/updates/packages/
sudo rpm -Uvf --force docker-io-0.11.1-1.fc20.x86_64.rpm
The conflict probably also exists in rawhide. (unverified)
The upstream binary in both packages is 'docker'. Debian/Ubuntu rename their
binary to 'docker-io' to deal with the conflict.
There is a plan to replace the 'docker' package with a renamed 'wmdocker'
package in F21. (Bug # 1043676). However, that will take until F23 release to
complete the Obsoletes/Expires process. In the meantime, any user with docker
from F20 or rawhide will be unable to install docker-io, unless they use the
workaround.
Related issues:
* https://fedorahosted.org/fpc/ticket/341 "How to replace "docker" package with
an entirely different package of the same name?"
* https://bugzilla.redhat.com/show_bug.cgi?id=1043676 "drop docker from rawhide
(or redirect to wmdocker)"
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1176844] New: add ${FLANNEL_OPTIONS} to flanneld.service unitfile
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1176844
Bug ID: 1176844
Summary: add ${FLANNEL_OPTIONS} to flanneld.service unitfile
Product: Fedora
Version: rawhide
Component: flannel
Severity: medium
Assignee: jchaloup(a)redhat.com
Reporter: jeder(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, linville(a)redhat.com,
lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1175660] SELinux is preventing /usr/bin/ping from 'read' accesses on the file hosts.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1175660
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
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
Component|selinux-policy |docker-io
Assignee|mgrepl(a)redhat.com |lsm5(a)redhat.com
--- Comment #3 from Daniel Walsh <dwalsh(a)redhat.com> ---
Lokesh can you see if this is fixed in docker-io-1.4?
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 5 months