Please open a new bug for your issue, using 'ubuntu-bug lxc' (though
actually I am suspecting a dnsmasq bug). It may be the same issue as
this bug, but many variables are different.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
On an 800 Mhz machine I can quite consistently reproduce startup
failures and conflicting IPs with ext3 instead of btrfs with only two
containers.
Additional Information:
A brand new install of Ubuntu 13.04 Server AMD64 with all updates applied.
$ sudo lxc-ls --fancy
NAME STATEIPV4
So it sounds like the bug still exists in the latest Mainline kernel,
and it has been around since at lease the 3.2 kernel. Do you happen to
know if there was a previous release that did not exhibit this bug?
--
You received this bug notification because you are a member of Kernel
Packages,
I only started using lxc+btrfs in the past few months, so unfortunately
I have no information about the behavior of any previous kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Additional note: I've found the problem manifests more easily with the
following modified test script (this one forks all LXC clone/start
operations immediately):
test.sh:
#!/usr/bin/env bash
prefix=$1
test -z ${prefix} echo 'error: missing required parameter: prefix'
12
5 matches
Mail list logo
