Yes, the naming convention they have chosen makes looking for lxd information very difficult when the commands, file paths and conventions are different to the lxc predecessor/underlying programs.
But I think that has been discussed on this list before! From: lxc-users [mailto:[email protected]] On Behalf Of Michael Peek Sent: 20 October 2016 19:07 To: LXC users mailing-list Subject: Re: [lxc-users] LXC containers w/ static IPs work on some hosts, not on others I started out with lxd but ran into problems when I tried googling for instructions on how to assign a static IP address to a container. All of the instructions I found said to edit /var/lib/lxc/<container>/config, and there was no /var/lib/lxc/ directory. So I uninstalled lxd and installed lxc instead. Michael On 10/20/2016 01:59 PM, McDonagh, Ed wrote: I’m very much not a guru on this topic, but it strikes me to check if you are using lxc for a reason, rather than using lxd? If you don’t have a legacy reason, I don’t know why you wouldn’t want to use the new tools that are being developed. From: lxc-users [mailto:[email protected]] On Behalf Of Michael Peek Sent: 20 October 2016 18:57 To: LXC users mailing-list Subject: Re: [lxc-users] LXC containers w/ static IPs work on some hosts, not on others There is no lxc-profile command, and lxc-ls and lxc-info don't list anything about a profile. I have no idea if that means anything. Michael On 10/20/2016 01:53 PM, McDonagh, Ed wrote: It will be the new lxc software, but without the niceness of the lxd interface. Hence all his commands being lxc-command instead of lxc command From: lxc-users [mailto:[email protected]] On Behalf Of Ron Kelley Sent: 20 October 2016 18:51 To: LXC users mailing-list Subject: Re: [lxc-users] LXC containers w/ static IPs work on some hosts, not on others hmmm, seems you are running the “original” version of lxc and not the new lxc/lxd software. Please ignore my comments then… On Oct 20, 2016, at 1:47 PM, Michael Peek <[email protected]<mailto:[email protected]>> wrote: # lxc profile show The program 'lxc' is currently not installed. You can install it by typing: apt install lxd-client Maybe that's part of the problem? Am I missing a package? Here are the packages I have installed for lxc: # dpkg -l | grep lxc | cut -c1-20 ii liblxc1 ii lxc ii lxc-common ii lxc-templates ii lxc1 ii lxcfs ii python3-lxc Michael On 10/20/2016 01:43 PM, Ron Kelley wrote: "lxc profile show”. Usually, you have a default profile that gets applied to your container unless you have created a new/custom profile. On Oct 20, 2016, at 1:41 PM, Michael Peek <[email protected]<mailto:[email protected]>> wrote: How do I tell? Michael On 10/20/2016 01:35 PM, Ron Kelley wrote: What profile(s) are you using for your LXC containers? On Oct 20, 2016, at 1:33 PM, Michael Peek <[email protected]<mailto:[email protected]>> wrote: Hi gurus, I'm scratching my head again. I'm using the following commands to create an LXC container with a static IP address: # lxc-create -n my-container-1 -t download -- -d ubuntu -r xenial -a amd64 # vi /var/lib/lxc/my-container-1/config Change: # Network configuration # lxc.network.type = veth # lxc.network.link = lxcbr0 # lxc.network.flags = up # lxc.network.hwaddr = 00:16:3e:0d:ec:13 lxc.network.type = macvlan lxc.network.link = eno1 # vi /var/lib/lxc/my-container-1/rootfs/etc/network/interfaces Change: #iface eth0 inet dhcp iface eth0 inet static address xxx.xxx.xxx.4 netmask 255.255.255.0 network xxx.xxx.xxx.0 broadcast xxx.xxx.xxx.255 gateway xxx.xxx.xxx.1 dns-nameservers xxx.xxx.0.66 xxx.xxx.128.66 8.8.8.8 dns-search my.domain # lxc-start -n my-container-1 -d It failed to work. I reviewed my notes from past posts to the list but found no discrepancies. So I deleted the container and tried it on another host -- and it worked. Next I deleted that container and went back to the first host, and it failed. Lastly, I tried the above steps on multiple hosts and found that it works fine on some hosts, but not on others, and I have no idea why. On hosts where this fails there are no error messages, but the container can't access the network, and nothing on the network can access the container. Is there some step that I'm missing? Thanks for any help, Michael Peek _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users ________________________________ Attention: This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary, confidential and/or privileged information and should not be copied, disclosed, distributed, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and delete this e-mail (including attachments and copies). The statements and opinions expressed in this e-mail are those of the author and do not necessarily reflect those of the Royal Marsden NHS Foundation Trust. The Trust does not take any responsibility for the statements and opinions of the author. Website: http://www.royalmarsden.nhs.uk ________________________________ _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users ________________________________ Attention: This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary, confidential and/or privileged information and should not be copied, disclosed, distributed, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and delete this e-mail (including attachments and copies). The statements and opinions expressed in this e-mail are those of the author and do not necessarily reflect those of the Royal Marsden NHS Foundation Trust. The Trust does not take any responsibility for the statements and opinions of the author. Website: http://www.royalmarsden.nhs.uk ________________________________ _______________________________________________ lxc-users mailing list [email protected]<mailto:[email protected]> http://lists.linuxcontainers.org/listinfo/lxc-users ######################################################################### Attention: This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary, confidential and/or privileged information and should not be copied, disclosed, distributed, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and delete this e-mail (including attachments and copies). The statements and opinions expressed in this e-mail are those of the author and do not necessarily reflect those of the Royal Marsden NHS Foundation Trust. The Trust does not take any responsibility for the statements and opinions of the author. Website: http://www.royalmarsden.nhs.uk #########################################################################
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
