[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 --- Comment #5 from Lukas Doktor --- Hi Daniel, it's not related to the image. I can use busybox as well. Also simple `docker pull busybox:latest` also generates multiple `update-packages` transactions. (starting after the first layer is downl

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 Daniel Walsh changed: What|Removed |Added CC||jonat...@jonmasters.org,

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 --- Comment #7 from Rex Dieter --- I would guess that *something* is talking to PackageKit via dbus. Hard to tell what that "something" is yet, without more extensive logging here. Probably depends on what is in the docker image and what it

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 --- Comment #8 from Lokesh Mandvekar --- Hmm, PackageKit isn't present in the fedora image (not sure about the other images though) bash-4.2# rpm -q PackageKit package PackageKit is not installed -- You are receiving this mail because: You

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 Rex Dieter changed: What|Removed |Added CC||ldok...@redhat.com Flags|

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 Lukas Doktor changed: What|Removed |Added Flags|needinfo?(ldok...@redhat.co | |m)

[Bug 1111189] yumBackend started with each `docker start`

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=189 --- Comment #11 from Lukas Doktor --- Created attachment 936228 --> https://bugzilla.redhat.com/attachment.cgi?id=936228&action=edit dbus-monitor --system output This is the `dbus-monitor --system` output. After the monitor started I execut

[Bug 1060454] Review Request: golang-github-armon-go-metrics - Collect run time and performance metrics in golang software

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1060454 Vincent Batts changed: What|Removed |Added CC||vba...@redhat.com --- Comment #3 from

[Bug 1140398] New: Catastrophic failure saving large images

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1140398 Bug ID: 1140398 Summary: Catastrophic failure saving large images Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: l...@fedoraproject.org

[Bug 1140405] New: systemctl start docker fails because systemd continuously restarts the daemon

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1140405 Bug ID: 1140405 Summary: systemctl start docker fails because systemd continuously restarts the daemon Product: Fedora Version: 20 Component: docker-io Assignee:

[Bug 1140405] systemctl start docker fails because systemd continuously restarts the daemon

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1140405 --- Comment #1 from Toshio Ernie Kuratomi --- Created attachment 936326 --> https://bugzilla.redhat.com/attachment.cgi?id=936326&action=edit Output of journalctl -u docker --no-pager -l Here's output from journalctl. You can see that at fir

[Bug 1140405] systemctl start docker fails because systemd continuously restarts the daemon

2014-09-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1140405 --- Comment #2 from Toshio Ernie Kuratomi --- Created attachment 936327 --> https://bugzilla.redhat.com/attachment.cgi?id=936327&action=edit Some systemctl status -l output here's a copy and paste of some runs of systemctl status -l while I