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 created, the log mount points are
added. What this means is that other users on the same machine will not
be able to mount the log directory as specified in the container lxc
config file, and the cgroup setting will fail.
One solution to this is to have a template container per user rather
than a shared one.
** Tags added: local lxc regression
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
--
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/juju-core/+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
