[Lxc-users] Containers are all getting same IP address

Jay Taylor jay at jaytaylor.com
Fri Aug 9 15:57:29 UTC 2013


Also, here is one of the container configs:

lxc.mount = /var/lib/lxc/sendhub_web_v7_10146/fstab
lxc.tty = 4
lxc.pts = 1024
lxc.devttydir = lxc
lxc.arch = x86_64
lxc.logfile = /var/log/lxc/sendhub_web_v7_10146.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 = sendhub_web_v7_10146
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = 00:16:3e:07:7b:8f
lxc.cap.drop = sys_module
lxc.cap.drop = mac_admin
lxc.cap.drop = mac_override
lxc.cap.drop = sys_time
lxc.rootfs = /var/lib/lxc/sendhub_web_v7_10146/rootfs
lxc.pivotdir = lxc_putold


On Fri, Aug 9, 2013 at 8:52 AM, Jay Taylor <jay at jaytaylor.com> wrote:

> Hi Serge,
>
> That's the thing..the containers all have unique addresses.  They're being
> created by `lxc-clone -B btrfs -s -o base_container -n <name>
>
> Now...every container I try to create or stop/start doesn't receive any IP
> address.  And all those duplicates no longer show any ip.
>
> here is lxc-ls --fancy:
>
>  sendhub                     STOPPED  -     -     NO
> sendhub_important_v7_10012  RUNNING  -     -     NO
> sendhub_important_v7_10019  RUNNING  -     -     NO
> sendhub_important_v7_10024  RUNNING  -     -     NO
> sendhub_important_v7_10054  RUNNING  -     -     NO
> sendhub_important_v7_10069  RUNNING  -     -     NO
> sendhub_important_v7_10074  RUNNING  -     -     NO
> sendhub_important_v7_10089  RUNNING  -     -     NO
> sendhub_important_v7_10094  RUNNING  -     -     NO
> sendhub_important_v7_10104  RUNNING  -     -     NO
> sendhub_important_v7_10129  RUNNING  -     -     NO
> sendhub_important_v7_10139  RUNNING  -     -     NO
> sendhub_important_v7_10144  RUNNING  -     -     NO
> sendhub_important_v7_10149  RUNNING  -     -     NO
> sendhub_important_v7_10164  RUNNING  -     -     NO
> sendhub_important_v7_10174  RUNNING  -     -     NO
> sendhub_important_v7_10179  RUNNING  -     -     NO
> sendhub_important_v7_10189  RUNNING  -     -     NO
> sendhub_scheduler_v7_10159  RUNNING  -     -     NO
> sendhub_web_v7_10029        RUNNING  -     -     NO
> sendhub_web_v7_10034        RUNNING  -     -     NO
> sendhub_web_v7_10039        RUNNING  -     -     NO
> sendhub_web_v7_10059        RUNNING  -     -     NO
> sendhub_web_v7_10064        RUNNING  -     -     NO
> sendhub_web_v7_10084        RUNNING  -     -     NO
> sendhub_web_v7_10099        RUNNING  -     -     NO
> sendhub_web_v7_10109        RUNNING  -     -     NO
> sendhub_web_v7_10114        RUNNING  -     -     NO
> sendhub_web_v7_10119        RUNNING  -     -     NO
> sendhub_web_v7_10134        RUNNING  -     -     NO
> sendhub_web_v7_10154        RUNNING  -     -     NO
> sendhub_web_v7_10169        RUNNING  -     -     NO
> sendhub_web_v7_10184        RUNNING  -     -     NO
> sendhub_worker_v7_10044     RUNNING  -     -     NO
> sendhub_worker_v7_10079     RUNNING  -     -     NO
> sendhub_worker_v7_10124     RUNNING  -     -     NO
> sendhub_worker_v7_10194     RUNNING  -     -     NO
> sendhub_worker_v7_10199     RUNNING  -     -     NO
>
> What could have gone wrong here? I have 5/5 nodes, all in this state
> (meaning this problem has been reproduced across multiple hosts).
>
>
> On Fri, Aug 9, 2013 at 8:02 AM, Serge Hallyn <serge.hallyn at ubuntu.com>wrote:
>
>> Quoting Jay Taylor (jay at jaytaylor.com):
>> > Greetings,
>> >
>> > I am hitting a problem with LXC were it's assigned the same IP address
>> to
>> > different containers:
>>
>> How are you creating the containers?  You need to give each container a
>> unique mac address.  lxc-clone should do this for you, as should
>> lxc-create.  If you're manually copying the containers, then you'll
>> have to do it by hand.
>>
>> can you show the lxc.network sections of two of the containers, and
>> the commands you used to create them?
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20130809/d9be8c65/attachment.html>


More information about the lxc-users mailing list