Quoting Frederico Araujo ([email protected]): > Hi, > > I've been using LXC for over two years without problems. This week, I > upgraded my Ubuntu from Trusty to Vivid, and I noticed that my overlayfs > containers stopped getting IP assigned. In my machine the error can be > reproduced in this way: > > 1. lxc-create -n base -t ubuntu
Do you have this problem if you use the download template? > 2. Edit ubuntu/config to add lxc.aa_profile = unconfined interesting that it has to be unconfined. if you tail -f /var/log/syslog and then start the container, does the tail -f output show any DENIED messages? > 3. lxc-clone -s -B overlayfs ubuntu tmp Does the 'ubuntu' container start ok? > 4. lxc-start -n tmp -d > 5. lxc-ls -f shows: > > NAME STATE IPV4 IPV6 GROUPS AUTOSTART > ----------------------------------------------------------------------- > tmp RUNNING - *(no IP)* - - NO > ubuntu STOPPED - - - NO Are you able to lxc-attach -n tmp and look around? what does 'ps -ef' and 'ifconfig -a' show? > Interestingly, I don't run into this issue when running the container in > confined mode (without lxc.aa_profile = unconfined). I checked past threads > in this list and in launchpad, and noticed that some people had problems > with overlayfs when upgrading to vivid, but it seems that these problems > were fixed in LXC 1.1 release. I'm running on LXC 1.1.2. > > Any thoughts? > > Thanks, > Fred > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
