It would appear that the problem happens because of twistd's default
behavior when daemonizing. It always sets umask to 0077. On non-local
images, we don't daemonize because the agents are run via upstart in
--nodaemonize mode.
I have a fix for this in the local-cloud-img branch, which is to
explicitly set the umask back to 0022. This might also have the effect
of opening up the permissions a bit on the lxc containers so normal
users can poke around in the rootfs if they have sufficient perms
(though that may not be desirable since uids will not match up
properly).
** Branch linked: lp:~clint-fewbar/juju/local-cloud-img
** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
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/930430
Title:
lxc-ls requires root access after deploying an LXC instance
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/930430/+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
