LXD container with snap in Proxmox LXC container?

yurtesen

Active Member
Nov 14, 2020
38
5
28
I am using Proxmox 7.1 and Ubuntu 20.04 in the CT

I found: https://forum.proxmox.com/threads/ubuntu-snaps-inside-lxc-container-on-proxmox.36463/#post-230060
and I have installed LXD in Proxmox CT. It mostly seems to work fine.

But the services do not completely start with Ubuntu 20.04 CT. (blah is the LXD container inside Proxmox CT container)


Code:
root@blah:~# systemctl list-jobs
JOB UNIT                                 TYPE  STATE
2   multi-user.target                    start waiting
230 systemd-logind.service               start running
1   graphical.target                     start waiting
77  systemd-update-utmp-runlevel.service start waiting

4 jobs listed.
root@blah:~#

and

Code:
Dec 15 13:12:04 blah systemd[1]: Starting Login Service...
Dec 15 13:12:04 blah systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 15 13:12:04 blah systemd-logind[153]: New seat seat0.
Dec 15 13:13:34 blah systemd[1]: systemd-logind.service: start operation timed out. Terminating.
Dec 15 13:13:34 blah systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 15 13:13:34 blah systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Dec 15 13:13:34 blah systemd[1]: Failed to start Login Service.
Dec 15 13:13:34 blah systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 3.
Dec 15 13:13:34 blah systemd[1]: Stopped Login Service.

Is there a way to fix this? Because commands like "systemctl isolate multi-user.target" just wait forever and hang.
 
Last edited:
Code:
Dec 15 01:30:48 blah systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 15 01:30:49 blah networkd-dispatcher[114]: No valid path found for iwconfig
Dec 15 01:30:49 blah networkd-dispatcher[114]: No valid path found for iw
Dec 15 01:30:49 blah networkd-dispatcher[114]: Traceback (most recent call last):
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/bin/networkd-dispatcher", line 497, in <module>
Dec 15 01:30:49 blah networkd-dispatcher[114]:     init()
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/bin/networkd-dispatcher", line 494, in init
Dec 15 01:30:49 blah networkd-dispatcher[114]:     main()
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/bin/networkd-dispatcher", line 478, in main
Dec 15 01:30:49 blah networkd-dispatcher[114]:     dispatcher.register()
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/bin/networkd-dispatcher", line 252, in register
Dec 15 01:30:49 blah networkd-dispatcher[114]:     bus = dbus.SystemBus()
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__
Dec 15 01:30:49 blah networkd-dispatcher[114]:     return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop,
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__
Dec 15 01:30:49 blah networkd-dispatcher[114]:     bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
Dec 15 01:30:49 blah networkd-dispatcher[114]:   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__
Dec 15 01:30:49 blah networkd-dispatcher[114]:     bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
Dec 15 01:30:49 blah networkd-dispatcher[114]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Failed to query AppArmor policy: Permission denied
Dec 15 01:30:49 blah systemd[1]: networkd-dispatcher.service: Main process exited, code=exited, status=1/FAILURE
Dec 15 01:30:49 blah systemd[1]: networkd-dispatcher.service: Failed with result 'exit-code'.