I was able to For stage two, at least with systemd, I changed
/lib/systemd/system/lxd-startup.service to:
[Unit]
Description=Container hypervisor based on LXC - boot time check
After=cgmanager.service lxd-unix.socket
Requires=cgmanager.service lxd-unix.socket
[Service]
Type=oneshot
ExecStart=/usr/bin/lxd activateifneeded
TimeoutSec=30s
[Install]
WantedBy=multi-user.target
while removing the files
/etc/systemd/system/multi-user.target.wants/lxc-net.service
/etc/systemd/system/multi-user.target.wants/lxc.service
(i.e. in packaging we would remove
[Install]
WantedBy=multi-user.target
from /lib/systemd/system/lxc{,-net}.service)
Now when the system comes up, lxcbr0 is not there. When I do 'lxc
list', it comes up.
A user who wants to use non-lxd lxc can do
sudo systemctl add-wants multi-user.target lxc.service
to make lxc and lxc-net start back up at boot.
The lxd-startup.service also still works, since it works by activating
lxd if the database shows containers need to be started.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image produces broken lxc (and later lxd)
containers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
