[Bug 1243479] New: RFE: Ship docker with all RHEL patches
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1243479
Bug ID: 1243479
Summary: RFE: Ship docker with all RHEL patches
Product: Fedora
Version: 22
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: riek(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,
mgoldman(a)redhat.com, miminar(a)redhat.com,
msamia(a)netsuite.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com, wolfy(a)nobugconsulting.ro
In order to ensure that cross-development works for RHEL on Fedora, please ship
docker with all the same patches currently shipped or planned to be shipped in
RHEL.
Specifically please include the secrets patch to allow using RHEL subscriptions
to develop RHEL containers on top of a Fedora workstation.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 10 months
[Bug 1046469] New: docker privileged mode with cmd /sbin/init - agetty & high cpu
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1046469
Bug ID: 1046469
Summary: docker privileged mode with cmd /sbin/init - agetty &
high cpu
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: fortuik(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:
docker containers in privileged mode mess with the host agetty and produce very
hicht cpu load
Version-Release number of selected component (if applicable):
Fedora 20
Docker 0.7.1, 0.7.2
How reproducible:
docker run -privileged -d mattdm/fedora:latest /sbin/init
Actual results:
docker container runs
cpu load is very high - agetty
stopping the container & the docker daemon do not free the cpu resources
one have to kill the agetty process
Expected results:
docker container runs
Additional info:
In my real case i run rhel containers with puppet & ssh daemons for a small
puppet lab.
The reason i met this bug is that running docker container with /sbin/init cmd
under RHEL 6.5 require priviliged mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 10 months
[Bug 1192081] New: Modify base image Dockerfile to enable systemd to run smoothly
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1192081
Bug ID: 1192081
Summary: Modify base image Dockerfile to enable systemd to run
smoothly
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: vpavlin(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:
systemd requires container=docker set in env and /run, /tmp to be mountpoints
start successfully. In my opinion, we should add
ENV container=docker
VOLUME ['/run', '/tmp']
to the base image Dockerfile.
Command
docker run --it --rm -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora:rawhide
/usr/sbin/init
would then be all an user would need to "boot" systemd in a container.
I've already made some changes in KS file - remove fstab and machine-id, mask
mount units... which make the boot sequence smooth.
More changes to boot sequence will probably come later (f.e. switch from
graphical.target to multi-user target)
I'd also like to suggest new Rawhide build to be pushed to registry. This one
works for me quite well:
http://koji.fedoraproject.org/koji/taskinfo?taskID=8883309
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 10 months
[Bug 1342820] New: Cannot running Docker on Red Hat 6.5
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1342820
Bug ID: 1342820
Summary: Cannot running Docker on Red Hat 6.5
Product: Fedora EPEL
Version: el6
Component: docker-io
Severity: high
Assignee: ichavero(a)redhat.com
Reporter: ctminh070193(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,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com,
wolfy(a)nobugconsulting.ro
Description of problem:
Cannot run Docker after installation
Version-Release number of selected component (if applicable):
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d/1.7.1
OS/Arch (client): linux/amd64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Get http:///var/run/docker.sock/v1.19/version: dial unix /var/run/docker.sock:
no such file or directory. Are you trying to connect to a TLS-enabled daemon
without TLS?
Expected results:
fix the problem successfully
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 10 months