https://bugzilla.redhat.com/show_bug.cgi?id=1214731
Bug ID: 1214731
Summary: Tracker for golang-github-spf13-pflag
Product: Fedora
Version: rawhide
Component: golang-github-spf13-pflag
Assignee: lsm5(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-spf13-pflag 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=1214784
Bug ID: 1214784
Summary: Tracker for golang-github-prometheus-client_golang
Product: Fedora
Version: rawhide
Component: golang-github-prometheus-client_golang
Assignee: jchaloup(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-prometheus-client_golang 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=1222796
Bug ID: 1222796
Summary: Tracker for golang-github-cpuguy83-go-md2man
Product: Fedora
Version: rawhide
Component: golang-github-cpuguy83-go-md2man
Severity: low
Priority: low
Assignee: lsm5(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jcajka(a)redhat.com,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-cpuguy83-go-md2man 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=1215656
Bug ID: 1215656
Summary: Tracker for golang-github-fsouza-go-dockerclient
Product: Fedora
Version: rawhide
Component: golang-github-fsouza-go-dockerclient
Assignee: lsm5(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, eparis(a)redhat.com,
extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-fsouza-go-dockerclient 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=1204620
Bug ID: 1204620
Summary: container stays around wihtout any processes in it
Product: Fedora
Version: 22
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: mvollmer(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
Created attachment 1005245
--> https://bugzilla.redhat.com/attachment.cgi?id=1005245&action=edit
Setup script for reproducing
Description of problem:
When running a specific custom image (see attachement), docker fails to notice
when the single process exits. The container stays around, and attempts to
stop or remove it result in errors.
Doing the same with a slightly older version of docker shows expected behavior.
Version-Release number of selected component (if applicable):
docker-io-1.5.0-19.git5d7adce.fc22.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Run the attached SETUP script in an empty directory
2. Run the resulting image
# docker run --name=probe cp /bin/container-probe
3. After wrestling control back from the hanging "docker run",
try to stop or remove the container.
# docker stop probe
# docker rm -f probe
Actual results:
The expected output of container-probe is shown, but "docker run ..." does not
return to the command line prompt. In fact, job control doesn't work anymore
either (C-c, C-z, C-\).
Stopping and removing leads to these errors:
# docker stop probe
Error response from daemon: Cannot stop container probe: active container for
c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist
FATA[0000] Error: failed to stop one or more containers
# docker rm -f probe
Error response from daemon: Could not kill running container, cannot remove -
active container for
c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist
FATA[0000] Error: failed to remove one or more containers
Expected results:
The output is shown and "docker run" terminates successfully, the container is
show as "exited" and can be removed.
Additional info:
docker-io-1.5.0-1.fc21.x86_64 shows the expected behavior.
"docker run -i" return control to the shell, but the resulting container can't
be stopped or removed either.
"systemctl restart docker" puts the "probe" container into a state where it can
be removed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1145659
Bug ID: 1145659
Summary: [PATCH] Support /etc/sysconfig/docker-storage
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: walters(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, dwalsh(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, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com,
virt-bugs(a)redhat.com
Depends On: 1144206
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1144206
[Bug 1144206] [PATCH] Support /etc/sysconfig/docker-storage
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096296
Bug ID: 1096296
Summary: man page inaccuracy about --sig-proxy and --tty
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: admiller(a)redhat.com, 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, whenry(a)redhat.com
Depends On: 1087697
+++ This bug was initially created as a clone of Bug #1087697 +++
Description of problem:
Hi guys,
the man page states:
--sig-proxy=true: Proxify all received signal to the process (even
in non-tty mode)
But the real behavior is, that sig-proxy doesn't work when --tty=true. It
should be mentioned in there, taht --sig-proxy is incompatible with --tty.
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. man docker
Actual results:
man page says it works even in non-tty
Expected results:
man page warns that --tty can't be used with --sig-proxy
How to verify:
1. docker run --tty=true -i --rm fedora bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps -ax | grep docker
3. kill -SIGUSR1 $PID
4. (with --tty=true no signals are received, when you try the same with
--tty=false, signals are proxified and messages are displayed)
--- Additional comment from Lokesh Mandvekar on 2014-04-15 02:11:48 EDT ---
Copying William (he recently got per subcommand manpages merged upstream).
this seems to be the case even in the latest manpage (I'm guessing this was
inherited from the original manpage).
William, was there any discussion about this in your PR?
--- Additional comment from Lokesh Mandvekar on 2014-04-15 02:15:31 EDT ---
btw, the 0.10 rpm includes the latest manpages (should be in yum soon)
--- Additional comment from Lukas Doktor on 2014-04-15 04:45:55 EDT ---
Thanks for a quick reply. I tried the docker-io-0.10.0-2.fc20.x86_64 which
says:
--sig-proxy=true|false:
When set to true, proxify all received signals to the process
(even in non-tty mode). The default is true.
I'd really like to change it to "only in non-tty" with possible warning that
--tty=true is incompatible with --sig-proxy.
--- Additional comment from William Henry on 2014-04-30 15:54:25 EDT ---
I go this text from upstream. I'll check.
--- Additional comment from William Henry on 2014-04-30 16:02:22 EDT ---
Lukas,according to the folks upstream, this is a bug in docker run and attach.
It should be as the text suggests.
Can you file a bug upstream with docker? Here:
https://github.com/dotcloud/docker/issues
Please just take the information you posted above and post it there.
Thanks. Well spotted.
Best,
William
--- Additional comment from Lukas Doktor on 2014-05-02 04:02:01 EDT ---
Upstream tracer:
https://github.com/dotcloud/docker/issues/5547
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1087697
[Bug 1087697] man page inaccuracy about --sig-proxy and --tty
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096276
Bug ID: 1096276
Summary: signal 27 (SIGPROF) not passed to container using
--sig-proxy
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: admiller(a)redhat.com, 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
Depends On: 1087720
+++ This bug was initially created as a clone of Bug #1087720 +++
Description of problem:
When I send signal 27 to the docker process, which is running with
--sig-proxy=true, it's not forwarded. Other signals are...
Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
docker-io-0.9.1-1.fc21.x86_64
upstream Docker version 0.10.0, build dc9c28f/0.10.0
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -27 $PID
Actual results:
nothing
Expected results:
Received 27, ignoring...
Additional info:
When you send any other signal (apart from 19 or 9) it works fine.
--- Additional comment from Lukas Doktor on 2014-04-15 04:59:24 EDT ---
The signal 17 is also ignored.
--- Additional comment from Lukas Doktor on 2014-05-05 03:48:25 EDT ---
The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
[Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Bug ID: 1217613
Summary: Cannot start container [8] System error: mountpoint
for cpuset not found
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: jiri.folta(a)centrum.cz
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,
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 1020711
--> https://bugzilla.redhat.com/attachment.cgi?id=1020711&action=edit
screenshot of the error
Description of problem:
when trying to run a container using Cockpit I get "System error: mountpoint
for cpuset not found" error
Version-Release number of selected component (if applicable):
cockpit:
Version 0.27.
Built on Wed Mar 25 12:53:20 UTC 2015.
How reproducible:
allways
Steps to Reproduce:
1.Install minimal Fedora 21 for arm platform from
http://www.digitaldreamtime.co.uk/images/Fidora/21/
2.update the system
3.install cockpit and docker
4.login to the server using web interface https://ip:9090
5.download Image: docker.io/wordpress:latest
6. try running the image
Actual results:
you get an error message(attached)
Expected results:
actually running the image
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.