In that situation I see: $ sudo lxc-ls --fancy NAME STATE IPV4 IPV6 AUTOSTART ------------------------------------------------------ ubuntu-local-machine-1 STOPPED - - YES
Trying to boot it manually reveals the problem: $ sudo lxc-start -n ubuntu-local-machine-1 lxc-start: No such file or directory - failed to mount '/home/ubuntu/.juju/local/log' on '/usr/lib/x86_64-linux-gnu/lxc/var/log/juju' lxc-start: failed to setup the mount entries for 'ubuntu-local-machine-1' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'ubuntu-local-machine-1' For testing I commented out the lxc.mount.entry for /home/ubuntu/.juju/local/log in /srv/lxc/ubuntu-local-machine-1/config, and tried to start the container again. It boots now, and starts cloud- init. I can't log in though, as ubuntu/ubuntu does not work and I don't know which account it created, so I stopped the container manually. At this point I don't know how to tell juju to re-poke that instance to continue the setup. Supposedly this is due to some AppArmor restriction? I don't see any REJECTs in dmesg, but failing to bind-mount with a non-default container path sounds like that? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1290920/+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
