Hide Forgot
Description of problem: dbus-daemon is not able to run inside systemd-nspawn, whether I configure it to run as root or leave it to drop privileges. Version-Release number of selected component (if applicable): systemd-37-13.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Run a F17 tree using systemd-nspawn on a F16 host, like this: systemd-nspawn -D $HOME/rawhide /bin/systemd systemd.log_level=debug Actual results: dbus-daemon dies on startup. If I configure dbus-daemon to run as root, it doesn't die, but I still see errors about dbus connections, and neither rsyslog nor NetworkManager work. Expected results: dbus-daemon should work normally
Do you see any error messages? Anything in the log files in the container?
This is caused by D-Bus failing entirely if the CAP_AUDIT_WRITE capability is missing. D-Bus should really not do that. Since the audit subsystem is not container aware it should take missing CAP_AUDIT_WRITE gracefully and not fail. Reassigning to D-Bus. There's a work-around available. Try "systemd-nspawn --capability=CAP_AUDIT_WRITE" and things should work. But this will cause audit msgs from the container spill into the hosts audit stream, which is not desirable.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Linked to https://bugs.freedesktop.org/show_bug.cgi?id=49062
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.