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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1250352
Bug ID: 1250352
Summary: golang: HTTP request smuggling in net/http library
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: amaris(a)redhat.com
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
There have been found potentially exploitable flaws in Golang net/http library
affecting versions 1.4.2 and 1.5.
Problems:
* Double Content-length headers in a request does not generate a 400 error, the
second Content-length is ignored.
* Invalid headers are parsed as valid headers (like "Content Length:" with a
space in the middle)
Exploitations:
In a situation where the net/http agent HTTP communication with the final
http clients is using some reverse proxy (reverse proxy cache, SSL
terminators, etc), some requests can be made exploiting the net/http HTTP
protocol violations.
Attacker could possibly:
* bypass security controls on theses previous elements
* perform some cache poisoning on these elements
* alter the request/response map on these previous elements (for DOS)
CVE request:
http://seclists.org/oss-sec/2015/q3/237
Upstream patches:
https://github.com/golang/go/commit/117ddcb83d7f42d6aa72241240af99ded81118e9https://github.com/golang/go/commit/300d9a21583e7cf0149a778a0611e76ff7c6680fhttps://github.com/golang/go/commit/143822585e32449860e624cace9d2e521deee62e
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1256978
Bug ID: 1256978
Summary: cadvisor-0.16.0.1 is available
Product: Fedora
Version: rawhide
Component: cadvisor
Keywords: FutureFeature, Triaged
Assignee: jchaloup(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Latest upstream release: 0.16.0.1
Current version/release in rawhide: 0.16.0-1.fc23
URL: https://github.com/google/cadvisor
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1330110
Bug ID: 1330110
Summary: Tracker for golang packaging issues
Product: Fedora
Version: rawhide
Component: golang
Keywords: Tracking
Assignee: jchaloup(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, amurdaca(a)redhat.com,
golang(a)lists.fedoraproject.org, jcajka(a)redhat.com,
lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io,
vbatts(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1250485
Bug ID: 1250485
Summary: Tracker for golang-github-influxdb-influxdb
Product: Fedora
Version: rawhide
Component: golang-github-influxdb-influxdb
Assignee: fpokorny(a)redhat.com
Reporter: fpokorny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Tracker for async updates of golang-github-influxdb-influxdb 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=1249030
Bug ID: 1249030
Summary: Tracker for golang-github-ghodss-yaml
Product: Fedora
Version: rawhide
Component: golang-github-ghodss-yaml
Assignee: fpokorny(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Tracker for async updates of golang-github-ghodss-yaml 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=1250461
Bug ID: 1250461
Summary: Tracker for golang-github-grpc-grpc-go
Product: Fedora
Version: rawhide
Component: golang-github-grpc-grpc-go
Assignee: fpokorny(a)redhat.com
Reporter: fpokorny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com
Tracker for async updates of golang-github-grpc-grpc-go 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=1316210
Bug ID: 1316210
Summary: Cannot set dm.basesize until docker has been started
Product: Fedora
Version: rawhide
Component: docker-io
Severity: medium
Assignee: ichavero(a)redhat.com
Reporter: mason.jones(a)creditkarma.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:
When using terraform to bring up a new EC2 instance with Docker, I wanted to
modify the dm.basesize option before starting Docker. To do this, my script
adds a line to the /etc/sysconfig/docker-storage file:
DOCKER_STORAGE_OPTIONS= --storage-opt dm.basesize=50G
However, when it then tries to start Docker with systemctl start docker.service
I was getting an error:
Error starting daemon: error initializing graphdriver: Unknown option
dm.basesize
I had used this same line before, but realized that it was after Docker had
been started at least once on the server. So then I changed things to:
systemctl start docker.service
Add the line to /etc/sysconfigdocker-storage
systemctl restart docker.service
This works fine. Maybe Docker needs to be started at least once on the server
in order to initialize the storage subsystem somehow? Before that's done, it
doesn't recognize the storage option. This is sort of crazy, so is there a
proper fix/workaround?
Version-Release number of selected component (if applicable):
Output of "docker version": Docker version 1.7.1, build 446ad9b/1.7.1
This is on AWS EC2, running CentOS Linux release 7.1.1503 (Core).
I first asked this as an issue against Docker
(https://github.com/docker/docker/issues/21037) but they said since it's a Red
Hat-supported build of Docker it should be asked here.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1192848
Bug ID: 1192848
Summary: docker no longer supports socket-activation
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: tim(a)gfxmonk.net
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.4.1-8.fc21.x86_64
How reproducible:
Always
Steps to Reproduce:
$ docker ps
Actual results:
FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this
host?
Expected results:
/var/run/docker.sock should automatically start `docker.service` via socket
activation. This was the case on fedora 20.
Additional info:
I looked in the package history, and it looks like it was disabled by:
commit aecb9bfe55824e2c9c7be4afce3ac8dd7e3395f5
Author: Lokesh Mandvekar <lsm5(a)fedoraproject.org>
Date: Fri Jan 16 17:06:40 2015 +0000
docker group and socket activation not used
NVR: docker-io-1.4.1-7
- sysconfig file updates
Signed-off-by: Lokesh Mandvekar <lsm5(a)fedoraproject.org>
I assume there's a reason for this, but there's no bugzilla or other issue
reference, and no description of why the functionality should be removed. The
removal of socket activation is pretty annoying, so it would be great if it
could be re-enabled. If it can't be enabled, it would be good to document why.
--
You are receiving this mail because:
You are on the CC list for the bug.