Description of problem: I've just upgraded from FC30 to FC31 and from docker to moby-engine. Since then I get three lines in the system log every 30 seconds by moby-engine, which polutes the system log. Version-Release number of selected component (if applicable): moby-engine-18.09.8-2.ce.git0dd43dd.fc31.x86_64 How reproducible: Always. Just run container. Steps to Reproduce: 1. Just run container with moby-engine. 2. 3. Actual results: Jan 12 10:51:41 manicminer systemd[3933]: run-docker-runtime\x2drunc-moby-cda1b25b2baef0c4c971109229d5684dd5b2347ea7a73e6100b86869066b5daf-runc.SMvAzR.mount: Succeeded. Jan 12 10:51:41 manicminer systemd[4254]: run-docker-runtime\x2drunc-moby-cda1b25b2baef0c4c971109229d5684dd5b2347ea7a73e6100b86869066b5daf-runc.SMvAzR.mount: Succeeded. Jan 12 10:51:41 manicminer systemd[1]: run-docker-runtime\x2drunc-moby-cda1b25b2baef0c4c971109229d5684dd5b2347ea7a73e6100b86869066b5daf-runc.SMvAzR.mount: Succeeded. Expected results: No logs at all, or at least less. Additional info: This did not happen with docker.
Hi, Sorry for the delay. Do you still have these log lines? I cannot reproduce it. It may be due to a change in runc (2:1.0.0-102.dev.gitdc9208a.fc31)
Yes, I still have these log lines.
Thanks; I've just found the upstream issue: https://github.com/docker/for-linux/issues/679
The upstream fix https://github.com/owntracks/docker-recorder/pull/38 is 16 days old. When will it be integrated into Fedora and a new package rolled out?
https://github.com/owntracks/docker-recorder/pull/38 is not an upstream fix. This is a fix in a 3rd-party Dockerfile.
Any progress on this topic?
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.