Quoting Kapil Thangavelu (930...@bugs.launchpad.net): > I've just noticed this with some of the unit tests, afaik this is some > change in lxc behavior.
I don't think it's a change in lxc behavior. I think it's a change in the umask which juju has set when it calls lxc-start. lxc passes a requested mode to mkdir(2), which then &s that with the umask. Ideally juju would set umask correctly. There are two ways lxc could help, but they're not particularly palatable. It could second-guess the caller and hand-set umask before calling mkdir. I think that's Wrong. It could check umask and spit out an error if it is too restrictive. That will help users find the cause more quickly, but doesn't solve the bug. -- 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