[Bug 1266809] Re: adt-virt-lxc fails on Trusty
Martin Pitt
martin.pitt at ubuntu.com
Thu Jan 23 17:37:43 UTC 2014
I run adt-run as root with adt-virt-lxc, as in trusty, lxc-* now use
some kind of "user mode containers" where it looks for containers in
~/.local/share/lxc/ . So that doesn't work as intended any more anyway.
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => Low
** Changed in: autopkgtest (Ubuntu)
Status: New => Triaged
** Summary changed:
- adt-virt-lxc fails on Trusty
+ trusty: adt-virt-lxc cannot read /var/lib/lxc/ when running as user
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1266809
Title:
trusty: adt-virt-lxc cannot read /var/lib/lxc/ when running as user
Status in “autopkgtest” package in Ubuntu:
Triaged
Bug description:
adt-virt-lxc assumes that the unprivileged user can see inside
/var/lib/lxc in order to see when the guest container has finished
booting, by detecting cloud-init's boot-finished flag.
The newest lxc package locks down /var/lib/lxc by default, so this
breaks.
Hacked workaround: "sudo chmod 755 /var/lib/lxc". This reduces
security of the system, but I think it should be OK on single-user
systems, such as most environments where users are running adt-run.
To fix this properly, adt-virt-lxc needs to call out to sudo to check
for this flag, instead of calling os.path.exists, etc.
An even nicer fix would be for lxc to have this functionality. I have
filed bug 1266808 to track this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1266809/+subscriptions
More information about the foundations-bugs
mailing list