golang September 2014

golang@lists.fedoraproject.org

6 participants
290 discussions

[Bug 1088259] New: "docker top all" doesn't show processes when --tty=false
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1088259 Bug ID: 1088259 Summary: "docker top all" doesn't show processes when --tty=false 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: Hi guys, when I run docker with --tty=false, the `docker top $NAME all` doesn't show any processes (just headers). When using only `docker top $NAME` it shows them... Also the `ps` command inside container works, but `ps all` does not. Version-Release number of selected component (if applicable): docker-io-0.9.0-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -i --tty=false fedora bash 2. docker logs $NAME Actual results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND Expected results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 24006 23954 20 0 11732 540 - R pts/14 0:00 bash -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1111189] New: yumBackend started with each `docker start`
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1111189 Bug ID: 1111189 Summary: yumBackend started with each `docker start` 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, hushan.jia(a)gmail.com, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Hello guys, today I noticed 100% utilization followed by each `docker run` or `docker start`. It wasn't caused by the docker itself, but with each instance, yumBackend is executed. It never happened with older version. 4806 ? RN 0:00 /usr/bin/python /usr/share/PackageKit/helpers/yum/yuBackend.py get-updates none Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -t -i fedora bash 2. top 3. ps ax |grep yum Actual results: yumBackend is started and takes couple of secconds in 100% utilization 4806 ? RN 0:00 /usr/bin/python /usr/share/PackageKit/helpers/yum/yuBackend.py get-updates none Expected results: Apart from container no other processes should be started. (I can run `docker run -t -i fedora bash -c exit` which finishes immediately and the only process using cpu is the yumBackend process) Additional info: I tried executing `busybox sh`, `bash -c exit`, .... I even rebooted the machine but the results are the same. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1102751] New: Got "Error running removeDevice" after kill -9 docker
by Red Hat Bugzilla 29 May '15

29 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1102751 Bug ID: 1102751 Summary: Got "Error running removeDevice" after kill -9 docker 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: 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: While I was playing with Docker today, I found interesting behavior: When you 'kill -9' the 'docker -d' process, then this happens: 1. The 'docker -d' process gets killed ;-) 2. All containers gets killed 3. The 'docker -d' restarts, because of Restart=on-failure Now, while all this is expected and OK, I get this when I tried to 'restart' the container that was killed in 2): May 29 13:24:56 ip-10-146-193-102 systemd[1]: Starting Container origin-db-1... May 29 13:24:56 ip-10-146-193-102 sh[19731]: Reusing b80104263de02f39bbc6d742c977ddadecb0660f5c50386eaf1cf645f3515b9c May 29 13:25:07 ip-10-146-193-102 docker[19739]: Error: Cannot destroy container origin-db-1: Driver devicemapper failed to remove root filesystem e536cf328e0083e2414c750434deb1127517d00399fddac84903825d6f003787: Error running removeDevice May 29 13:25:07 ip-10-146-193-102 docker[19739]: 2014/05/29 13:25:07 Error: failed to remove one or more containers May 29 13:25:07 ip-10-146-193-102 gear[21193]: user: unknown user ctr-origin-db-1 May 29 13:25:09 ip-10-146-193-102 docker[21192]: 2014/05/29 13:25:09 Error: Cannot start container bd1a88a35e84ef6d71fa3e1df0b4e2998318dfed6d60fd3ae381567fff2ac2a3: Cannot find child for /origin-db-1 May 29 13:25:09 ip-10-146-193-102 systemd[1]: ctr-origin-db-1.service: main process exited, code=exited, status=1/FAILURE Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start up some containers 2. kill -9 (the 'docker -d' process pid) 3. Try to start the dead container again 4. Get the error above. Actual results: Expected results: Containers should be successfully started back. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1087700] New: lost signals when sending lots of signals using --sig-proxy to docker
by Red Hat Bugzilla 29 May '15

29 May '15

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.

1 15

[Bug 1093000] New: Unable to save an image to a tar archive
by Red Hat Bugzilla 29 May '15

29 May '15

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.

1 10

[Bug 1033604] New: Unable to start systemd service in Docker container
by Red Hat Bugzilla 19 May '15

19 May '15

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.

1 33

[Bug 1092136] New: Docker commands pause streaming audio
by Red Hat Bugzilla 28 Apr '15

28 Apr '15

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.

1 11

[Bug 1046717] New: Cancel run or pull operation doesn't actually stop the ongoing task
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1046717 Bug ID: 1046717 Summary: Cancel run or pull operation doesn't actually stop the ongoing task Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: lsm5(a)redhat.com Reporter: baptiste.millemathias(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: I've downloaded a docker image using "docker pull bradrydzewski/mongodb:2.4" and when I wanted to run it I did a "docker run bradrydzewski/mongodb" as the image name was named like that, and I saw docker pulling another image (the size was different), so I hit Ctrl+C thinking to going kill the operation. However a ps fax showed me dockerd was still downloading something, certainly image bradrydzewski/mongodb Version-Release number of selected component (if applicable): docker-io-0.7.0-14.fc20.x86_64 How reproducible: 100 % Steps to Reproduce: 1. docker pull bradrydzewski/mongodb:2.4 (let the complete operation happens) 2. docker run bradrydzewski/mongodb, and hit ctrl+c after few seconds Actual results: Dockerd still download image Expected results: docker client should ask Dockerd to cancel the download of the image -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1087704] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087704 Bug ID: 1087704 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Fedora Version: 20 Component: docker-io Severity: low 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: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. 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. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /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' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /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' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1087720] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087720 Bug ID: 1087720 Summary: signal 27 (SIGPROF) not passed to container using --sig-proxy 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 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-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. 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. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

← Newer
1
2
3
4
5
6
7
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang September 2014