unprivileged containers fail to start with 1.0.0~beta4-0ubuntu1

[James Hunt]

$ lxc-start -n trusty
lxc_container: Permission denied - failed to get real path for '/home/james/.local/share/lxc/trusty/rootfs'
lxc_container: failed to mount rootfs
lxc_container: failed to setup rootfs for 'trusty'
lxc_container: failed to setup the container
lxc_container: invalid sequence number 1. expected 2
lxc_container: failed to spawn 'trusty'

Downgrading to 1.0.0~beta3-0ubuntu1 fixes the problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.0~beta4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Fri Feb 7 11:15:30 2014
InstallationDate: Installed on 2010-10-21 (1205 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: lxc
UpgradeStatus: Upgraded to trusty on 2013-11-01 (97 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

[Serge Hallyn (serge-hallyn)]

Hi,

could you try it with

 lxc-start -n trusty -l trace -o out1

and attach out1 here?

 status: incomplete

[James Hunt (jamesodhunt)]

The problem does seem to be an LXC bug. However, I can work around it by changing the perms on my home directory from 0750 to 0755.

[Launchpad Janitor (janitor)]

This bug was fixed in the package lxc - 1.0.1-0ubuntu1

---------------
lxc (1.0.1-0ubuntu1) trusty; urgency=medium

  * New upstream bugfix release. (LP: #1246094, LP: #1277466)
    Changelog at: https://linuxcontainers.org/news
  * Add xz-utils to lxc-templates' dependencies.
 -- Stephane Graber <email address hidden> Fri, 07 Mar 2014 12:18:28 -0500

[Ivan Kozik (ludios)]

I was seeing the "Permission denied - failed to get real path for [...]" error on Ubuntu 14.04 with LXC 1.0.5-0ubuntu0.1 and linux-image-3.13.0-32-generic, and after some fruitless debugging, figured out I just needed to add +x permission on the container directory itself:

setfacl -m u:100000:x ~/ ~/.local ~/.local/share ~/.local/share/lxc ~/.local/share/lxc/CONTAINER

(It lacked +x because my umask was 007 instead of 002.)