[Lxc-users] clones of clones are failing to start

Jay Taylor jay at jaytaylor.com
Wed Jul 17 20:14:07 UTC 2013


Here it is, it is completely vanilla:

$ cat /var/lib/lxc/test_1/config
lxc.mount = /var/lib/lxc/test_1/fstab
lxc.tty = 4
lxc.pts = 1024
lxc.devttydir = lxc
lxc.arch = x86_64
lxc.logfile = /var/log/lxc/test_1.log
lxc.cgroup.devices.deny = a
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
lxc.cgroup.devices.allow = c 254:0 rm
lxc.cgroup.devices.allow = c 10:229 rwm
lxc.cgroup.devices.allow = c 10:200 rwm
lxc.cgroup.devices.allow = c 1:7 rwm
lxc.cgroup.devices.allow = c 10:228 rwm
lxc.cgroup.devices.allow = c 10:232 rwm
lxc.utsname = test_1
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = 00:16:3e:d8:0d:f2
lxc.cap.drop = sys_module
lxc.cap.drop = mac_test_1
lxc.cap.drop = mac_override
lxc.cap.drop = sys_time
lxc.rootfs = /var/lib/lxc/test_1/rootfs
lxc.pivotdir = lxc_putold


On Wed, Jul 17, 2013 at 1:07 PM, Tamas Papp <tompos at martos.bme.hu> wrote:

> On 07/17/2013 10:01 PM, Jay Taylor wrote:
> > Hi,
> >
> > I'm not sure what I am doing wrong here.
> >
> > This is a EC2 VM with /var/lib/lxc linking to a mounted BTRFS volume.
> >
> > OS: Ubuntu 12.04 LTS
> > LXC Version: 0.9.0
> > FS: BTRFS
> >
> > The current situation is that I have a base container, "base", which
> starts fine.  This has then
> > been cloned (with snapshot) to another container, e.g. "test".  "test"
> is also able to start fine.
> >  Then if I clone (again with snapshot) "test" to "test_1", and it won't
> start.
> >
> > Here is the output:
> > $ sudo lxc-start -n test_1
> > lxc-start: unknown capability mac_test_1
> > lxc-start: failed to drop capabilities
> > lxc-start: failed to setup the container
> > lxc-start: invalid sequence number 1. expected 2
> > lxc-start: failed to spawn 'test_1'
> >
> > I not yet sure why this is happening.  Do you know what might be causing
> this or how I might best
> > go about resolving it?
> >
>
> How does your config file looks?
>
> tamas
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20130717/52f3050e/attachment.html>


More information about the lxc-users mailing list