[Bug 1087700] New: lost signals when sending lots of signals using --sig-proxy to docker
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1087700
Bug ID: 1087700
Summary: lost signals when sending lots of signals using
--sig-proxy to docker
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.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, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
When I send lots of signals to the running docker with --sig-proxy (actual kill
signals, not `docker kill`), most of them got lost.
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
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. for AAA in `seq 1 32`; do [ $AAA -ne 9 ] && [ $AAA -ne 20 ] && [ $AAA -ne 19
] && kill -s $AAA $PID; done
Actual results:
Output of the docker is:
Received 1, ignoring...
Received 2, ignoring...
Expected results:
Messages for all of the `Received $NUM, ignoring...` printed (order doesn't
matter)
Additional info:
Skipping 9, 19, 20 as they are a bit too special..
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1093000] New: Unable to save an image to a tar archive
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1093000
Bug ID: 1093000
Summary: Unable to save an image to a tar archive
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: lslebodn(a)redhat.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:
I tried to dump content of docker image to a tarball with command "docker save"
It failed with error message "no space left on device"
Version-Release number of selected component (if applicable):
I was able to reproduce problem with docker-io from stable repository and with
docker-io from updates-testing
[root@vm-169 docker]# rpm -q docker-io
docker-io-0.9.1-1.fc20.x86_64
or
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
Allways
Steps to Reproduce:
1. Create big docker image (e.g. 1.8 GiB)
[root@vm-169 docker-freeipa]# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
big_image latest b366efe500de 57 minutes ago 1.778 GB
fedora 20 b7de3133ff98 5 days ago 372.7 MB
2. save docker image to tarball
[root@vm-169 docker]# docker save big_image > big_image.tar
Actual results:
[root@vm-169 docker]# docker save big_image > big_image.tar
2014/04/30 12:39:38 Error: write
/docker-export-085323451/934d868afd0a79629df2cad704cbc1ed9344654625569263a630933d2785de57/layer.tar:
no space left on device
[root@vm-169 docker]# file big_image.tar
big_image.tar: empty
[root@vm-169 docker]# ls -l big_image.tar
-rw-r--r--. 1 root root 0 Apr 30 13:41 big_image.tar
Expected results:
File big_image.tar should not be empty and should contain data from docker
image with name big_image
Additional info:
Directory /tmp should be used for creating small temporary files, because it is
mounted on tmpfs. I think it would be better to use /var/tmp in this case.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1033604] New: Unable to start systemd service in Docker container
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1033604
Bug ID: 1033604
Summary: Unable to start systemd service in Docker container
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: mfojtik(a)redhat.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,
vbatts(a)redhat.com
Description of problem:
Using Dockerfile like this:
FROM mattdm/fedora:latest
RUN yum update -y
RUN yum install -y redis
RUN systemctl enable redis.service
RUN systemctl start redis.service
EXPOSE 6379
ENTRYPOINT ["/usr/bin/redis-cli"]
The step 'systemctl start redis.service' failed with this error message:
Failed to get D-Bus connection: No connection to service manager.
Version-Release number of selected component (if applicable):
Name : docker-io
Arch : x86_64
Version : 0.7
Release : 0.17.rc6.fc20
Steps to Reproduce:
1. Save the above Dockerfile
2. Run: docker build -t test/redis .
3. The build fill faile on systemctl start.
Actual results:
The service failed to start due to D-BUS connection.
Expected results:
The service should be started?
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 11 months
[Bug 1092136] New: Docker commands pause streaming audio
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1092136
Bug ID: 1092136
Summary: Docker commands pause streaming audio
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: mdavis(a)redhat.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:
Execution of docker commands cause streaming audio to pause briefly (3-4
seconds)
Version-Release number of selected component (if applicable):
[root@dhcp81-173 ~]# rpm -q docker-io firefox flash-plugin
docker-io-0.9.1-1.fc20.x86_64
firefox-28.0-3.fc20.x86_64
flash-plugin-11.2.202.350-release.x86_64
[root@dhcp81-173 ~]# uname -s -r -v -m
Linux 3.13.10-200.fc20.x86_64 #1 SMP Mon Apr 14 20:34:16 UTC 2014 x86_64
How reproducible:
Nearly every docker command does this.
Steps to Reproduce:
1. Start up firefox and start listening to a streaming audio service (I
reproduced it on spotify.com, using the spotify web player)
2. Run a docker command. For example...
[root@dhcp81-173 ~]# docker images
REPOSITORY TAG IMAGE ID CREATED
VIRTUAL SIZE
10.3.76.138:5000/rhel6-base latest 60f3b7e9ba33 6 weeks
ago 1.437 GB
rhel6-base latest 60f3b7e9ba33 6 weeks
ago 1.437 GB
10.3.76.138:5000/rhel7b-base latest b96a0bc033bb 8 weeks
ago 827.9 MB
fedora rawhide 0d20aec6529d 12 weeks
ago 387 MB
fedora 20 58394af37342 12 weeks
ago 385.5 MB
fedora heisenbug 58394af37342 12 weeks
ago 385.5 MB
fedora latest 58394af37342 12 weeks
ago 385.5 MB
busybox latest 769b9341d937 12 weeks
ago 2.489 MB
[root@dhcp81-173 ~]# docker run 0d2 id
uid=0(root) gid=0(root) groups=0(root)
[root@dhcp81-173 ~]#
Actual results:
Currently playing audio paused for 3 seconds after running the 'id' command.
Expected results:
Uninterrupted audio playing
Additional info:
I'm running Fedora 20 XFCE build.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 11 months
[Bug 1184257] New: missing debug info
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1184257
Bug ID: 1184257
Summary: missing debug info
Product: Fedora
Version: rawhide
Component: etcd
Assignee: lacypret(a)gmail.com
Reporter: jan.kratochvil(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lacypret(a)gmail.com,
lemenkov(a)gmail.com, lsm5(a)redhat.com,
walters(a)redhat.com
Created attachment 982040
--> https://bugzilla.redhat.com/attachment.cgi?id=982040&action=edit
etcd.spec patch
Description of problem:
Current etcd.rpm contains neither debug info embedded nor separate
etc-debuginfo.rpm.
Version-Release number of selected component (if applicable):
etcd-2.0.0-1.rc1.fc22.x86_64 (not yet in Koji - that's Bug 1176138)
How reproducible:
Always
Steps to Reproduce:
yum install etcd
debuginfo-install etcd
$ readelf -wil /usr/lib/debug/usr/bin/etcd.debug
Actual results:
readelf: Error: '/usr/lib/debug/usr/bin/etcd.debug': No such file
$ readelf -wil /usr/bin/etcd # does not show anything anyway
Expected results:
Raw dump of debug contents of section .debug_line:
[...]
Contents of the .debug_info section:
[...]
Additional info:
Sure the goal is GDB, not readelf. But readelf is more foolproof.
Patch follows the debuginfo rules I have just updated at:
https://fedoraproject.org/w/index.php?title=PackagingDrafts%2FGo&diff=401...
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 11 months
[Bug 1202923] New: etcd and kubernetes dependency issue on fedora 21
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1202923
Bug ID: 1202923
Summary: etcd and kubernetes dependency issue on fedora 21
Product: Fedora
Version: 21
Component: etcd
Assignee: lacypret(a)gmail.com
Reporter: avagarwa(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lacypret(a)gmail.com,
lemenkov(a)gmail.com, lsm5(a)redhat.com,
walters(a)redhat.com
Description of problem:
Removing etcd on fedora 21 removes kubernetes too which should not happen
because etcd and kubernetes need not be co-located on the same system.
For example, I have following 3 VMs setup:
1. one is running as kube master on fedora 21
2. another is running as kube minion/node on fedora 21
3. third is running etcd inside a container on atomic host
Since based on above setup, On kube master, I wanted to remove etcd (as I do
not need etcd on kube master), but removing etcd removes kubernetes too.
Version-Release number of selected component (if applicable):
etcd-2.0.3-0.2.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1.remove/uninstall etcd on fedora 21 and it uninstall kubernetes too.
2.
3.
Actual results:
etcd and kubernetes are removed.
Expected results:
only etcd should be removed.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 12 months
[Bug 1205362] New: kubectl version outputs wrong version
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1205362
Bug ID: 1205362
Summary: kubectl version outputs wrong version
Product: Fedora
Version: 21
Component: kubernetes
Assignee: jchaloup(a)redhat.com
Reporter: avagarwa(a)redhat.com
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,
nhorman(a)redhat.com, vbatts(a)redhat.com
Description of problem:
kubectl version outputs wrong version
$ kubectl version
Client Version: version.Info{Major:"0", Minor:"12+",
GitVersion:"v0.12.0-1041-gef758881d108bb",
GitCommit:"ef758881d108bb53a128126c503689104d17f477", GitTreeState:"clean"}
Server Version: version.Info{Major:"0", Minor:"12+",
GitVersion:"v0.12.0-1041-gef758881d108bb",
GitCommit:"ef758881d108bb53a128126c503689104d17f477", GitTreeState:"clean"}
Version-Release number of selected component (if applicable):
kubernetes-0.13.2-0.3.gitef75888.fc23.x86_64
How reproducible:
always
Steps to Reproduce:
1. Install kubernetes-0.13.2-0.3.gitef75888.fc23.x86_64
2. run kubectl version
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 12 months
[Bug 1191438] New: docker-io-1.5.0 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1191438
Bug ID: 1191438
Summary: docker-io-1.5.0 is available
Product: Fedora
Version: rawhide
Component: docker-io
Keywords: FutureFeature, Triaged
Assignee: lsm5(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
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
Latest upstream release: 1.5.0
Current version/release in Fedora Rawhide: 1.4.1-27.git76baa35.fc22
URL: https://github.com/docker/docker/releases
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 Soon this service
will be implemented by a new system: https://release-monitoring.org/
It will require to manage monitored projects via a new web interface. Please
make yourself familiar with the new system to ease the transition.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years