Copying a Container from Host 1 to Host 2 - containers on both hosts get same IP address

[bmullan]

Describe the bug
On Host 1 I stopped container CN1
Then clicked COPY button and specified Host 2 with Container name CN1
When the copy was completed I notice the CN1 on Host 2 had the same IP as the CN1
on Host 1!

NOTE 1:
this was copying the actual container on Host 1 to Host 2 NOT copying a Snapshot from Host 1 to a container on Host 2.

Expected behavior
Copying a container from Host 1 to Host 2... the new container on Host 2 should get a new IP address.. not a duplicated one.

Screenshots
In the following:
Host CIAB = host with LXDMosaic on it and the original CN1 container
Host CIAB2 = the host I copied the original CN1 container TO.

NOTE 2:
If I manually copy Host1 CN1 to Host2 CN1 ... the Host 2 CN1 does get a new IP address:

bmullan@ciab:~$ lxc copy cn1 ciab2:cn1

Desktop (please complete the following information):
ubuntu 18.04.2 for all Hosts and containers

[turtle0x1]

How are you getting ip addresses, lxd dhcp?

[bmullan]

my 2nd server is set w just standard SNAP LXD so I would assume its just the regular LXD DNSMasq That's why I did the same function from the CLI to see if the resulting container also had a duplicate IP... but it did not. So either the API you use has a bug or there might be something you do that is missing/incorrect? Any, glad I caught that one as people would/could easily overlook it and then wonder why things are screwed up intermittently :-) brian

…

On Fri, Jul 5, 2019 at 11:32 AM turtle0x1 ***@***.***> wrote: How are you getting ip addresses, lxd dhcp? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#19?email_source=notifications&email_token=AAM23J6N7JCQO7XUSTZSVJ3P55SP7A5CNFSM4H6MBIA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZJZWBA#issuecomment-508795652>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAM23J7JHUTKL2UQ2XJDSJDP55SP7ANCNFSM4H6MBIAQ> .

[turtle0x1]

Ive run into an error I can't debug ive opened an issue on the lxd project. I could just being a idiot but I currently can't copy containers between two hosts!

[bmullan]

Just in LXDMosaic or using the CLI in a terminal? I'd make sure you can do it from the CLI first. Also don't forget the container has to be stopped (ie not running) or the copy will fail.

…

On Fri, Jul 5, 2019, 5:00 PM turtle0x1 ***@***.***> wrote: Ive run into an error I can't debug ive opened an issue on the lxd project. I could just being a idiot but I currently can't copy containers between two hosts! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#19?email_source=notifications&email_token=AAM23JY4F7556AWEY5Q2Z2LP56Y5FA5CNFSM4H6MBIA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKJWQQ#issuecomment-508861250>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAM23J5HKJMLA45QOXKNX6TP56Y5FANCNFSM4H6MBIAQ> .

[turtle0x1]

Works from the CLI its annoying

[turtle0x1]

I cant duplicate this can you check its still happening ?

[bmullan]

I will do it again but yes I duplicated it. Tried the first time using LXDMosaic & got duplicate IPs Deleted that container Manually copied container & it got new 10.x.x.x IP Deleted that container & tried again w LXDMosaic and again the container got a duplicate IP But I'll try it again Hopefully using same code as you were. Brian

…

On Fri, Jul 5, 2019, 7:40 PM turtle0x1 ***@***.***> wrote: I cant duplicate this can you check its still happening ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#19?email_source=notifications&email_token=AAM23J3JOX3XX4R2LEVGCBDP57LXPA5CNFSM4H6MBIA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKOLVI#issuecomment-508880341>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAM23J2XXC45EQ6BOYTY5ULP57LXPANCNFSM4H6MBIAQ> .

[turtle0x1]

@bmullan hey, been a while, hope your well!

This is actually expected behaviour according to stgraber, cleared this up in the following post;

https://discuss.linuxcontainers.org/t/extend-profile-with-container-specific-settings/8985/4

Sorry it took +1 year to resolve 😆

[turtle0x1]

Wait, Im wrong