https://bugzilla.redhat.com/show_bug.cgi?id=1111189
--- Comment #3 from Lukas Doktor <ldoktor(a)redhat.com> ---
Hi Lokesh, it's probably system-dependant, because I still see this failure and
it annoys me. After a while of spawning and removing containers I end up with
100% utilization which takes hours to finish. My /var/log/messages is full of:
Sep 5 10:18:47 t530 PackageKit: update-packages transaction /46549_daebdbbc
from uid 1000 finished with success after 3999ms
Sep 5 10:18:51 t530 PackageKit: update-packages transaction /46550_cdeacbdb
from uid 1000 finished with success after 3951ms
Sep 5 10:18:55 t530 PackageKit: update-packages transaction /46551_ecdabbbc
from uid 1000 finished with success after 4399ms
Sep 5 10:18:59 t530 PackageKit: update-packages transaction /46552_ccdcaedd
from uid 1000 finished with success after 3992ms
Sep 5 10:19:03 t530 PackageKit: update-packages transaction /46553_bedacbcd
from uid 1000 finished with success after 3986ms
Sep 5 10:19:07 t530 PackageKit: update-packages transaction /46554_ecaddbac
from uid 1000 finished with success after 4011ms
Sep 5 10:19:11 t530 PackageKit: update-packages transaction /46555_dbecccce
from uid 1000 finished with success after 3937ms
Right now I'm using docker-io-1.2.0-2.fc20.x86_64. Good thing is that when I
execute `yum clean all` it stops. Anyway once I start another container. Do you
know any method to see what asked for this yumBackend?
--
You are receiving this mail because:
You are on the CC list for the bug.