[SOLVED] LXC unprivileged Fedora 27 systemctl: Failed to connect to bus: No such file or directory

agaat

New Member
Aug 24, 2018
3
0
1
55
Hello,

recently, after upgrading both the container (unprivileged Fedora 27, although changing it to privileged doesn't change anything) and the host system, I can't get systemctl to work anymore in the container. Whenever I try to call it I get the error message:"Failed to connect to bus: No such file or directory". New containers exhibit the same behaviour.

I created an lxc log, the full log is to be long for this forum software, so I posted it here: pastebin.com/ahmiMVUr . The relevant log lines seem to be these:
Code:
lxc-start 102 20180824143905.133 NOTICE   start - start.c:start:2034 - Exec'ing "/sbin/init"
lxc-start 102 20180824143905.139 NOTICE   start - start.c:post_start:2045 - Started "/sbin/init" with pid "10875"
lxc-start 102 20180824143905.140 NOTICE   start - start.c:signal_handler:401 - Received 17 from pid 10815 instead of container init 10875
lxc-start 102 20180824144340.884 INFO     terminal - terminal.c:lxc_terminal_io_cb:373 - Terminal client on fd 8 has exited
lxc-start 102 20180824144340.884 ERROR    start - start.c:__lxc_start:1966 - Child process is not killed

Any help would be appreciated
 
Tried it here. To me this looks like a bug in their systemd version. Fedora 28 works again...
 
Interesting, I had already attempted to upgrade the container to Fedora 28 and was under the impression that the update had worked. After your comment I tried it again only to see that I was still using version 27. As you said, version 28 works fine. Thanks a lot for your answer!
 
There should be one available soon. In the mean time you can use one from lxc's images server. Just fetch the rootfs.tar.xz and give it a recognizable name, and put it in your template storage's template/cache/ dir.

[1] http://images.linuxcontainers.org/images/
 
  • Like
Reactions: MrJester888
There should be a fedora 28 template available now.
 
  • Like
Reactions: MrJester888