** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Summary changed:
- fails to start container with local provider with non-default LXC path
+ template container contains user log mount in error
--
You received this bug notification because you are a member of
It seems to me that the bug isn't in the different container directory,
but the way that the log directory is mounted.
I have just hit this same problem locally, and I don't have a non-
default directory.
What I do have though is two different users locally.
When the juju conatiner template is
** Changed in: juju-core
Milestone: None = next-stable
--
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
In that situation I see:
$ sudo lxc-ls --fancy
NAMESTATEIPV4 IPV6 AUTOSTART
--
ubuntu-local-machine-1 STOPPED - - YES
Trying to boot it manually reveals the problem:
$ sudo lxc-start -n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju (Ubuntu)
Status: New = Confirmed
--
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
