On Wed, Jan 20, 2016 at 05:48:52PM -0000, Tom Haddon wrote: > Public bug reported: > > I've followed https://help.ubuntu.com/lts/serverguide/lxc.html#lxc- > basic-usage but am getting a failure on lxc-start as follows: > > lxc-start -n container-test2 -F > lxc-start: start.c: print_top_failing_dir: 102 Permission denied - could not > access /home/mthaddon. Please grant it 'x' access, or add an ACL for the > container root. > lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 > lxc-start: start.c: __lxc_start: 1213 failed to spawn 'container-test2' > lxc-start: lxc_start.c: main: 344 The container failed to start. > lxc-start: lxc_start.c: main: 348 Additional information can be obtained by > setting the --logfile and --logpriority options. > > Is this because my home directory is encrypted? Which user is it trying > to connect as?
The container root, i.e. the first uid you put in /etc/subuid. If you grant access to that user (either by making it world +x or adding an acl as the message says), you should be able to launch a container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536297 Title: unable to lxc-start unprivileged LXC on wily due to permissions error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1536297/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
