Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation
On 19/10/16 07:10, David Favor wrote: > I'd prefer the "tweak each container config" approach. > Be great if someone could provide a URL for an example. Very hard to impossible to find examples of using lxc config to set the IP of each container and I'm still not sure it's even possible. Can anyone confirm this, and if so, provide an example? ATM what I do is either use dnsmasq to provide DHCP or stop the container and push a preconfigured interfaces file... lxc file push interfaces.tmp CONTAINER/etc/network/interfaces ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation
Mark Constable wrote: On 19/10/16 05:02, David Favor wrote: Looking for best way to change 10.87.167.115 to 144.217.33.224 (static/public IP). Prefer doing this in a way where communication between host/container + container/container works without adding iptables rules, which become complex to manage with many containers. The simplest way I am aware of is to set up your own bridge on a public IP range that you want to allocate and provide your own DHCP server that you have control over, or use lxc config to tweak the config of each container to provide it with a static IP as you go. I'd prefer the "tweak each container config" approach. Be great if someone could provide a URL for an example. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation
On 19/10/16 05:02, David Favor wrote: > Looking for best way to change 10.87.167.115 to 144.217.33.224 > (static/public IP). Prefer doing this in a way where communication > between host/container + container/container works without adding > iptables rules, which become complex to manage with many containers. The simplest way I am aware of is to set up your own bridge on a public IP range that you want to allocate and provide your own DHCP server that you have control over, or use lxc config to tweak the config of each container to provide it with a static IP as you go. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation
Many conflicting suggestions. Looking for documentation for how to accomplish the following. My project consists of migrating 100s of LXC containers to LXD, where each container has a static/public IP. ___ Environment + example test container... net12 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety net12 # lxd --version 2.4.1 net12 # lxc list +--+-+--+---++---+ | NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +--+-+--+---++---+ | yakkety-template | RUNNING | 10.87.167.115 (eth0) | fd42:1ad8:ce37:1b12:216:3eff:fe86:c4d4 (eth0) | PERSISTENT | 0 | +--+-+--+---++---+ ___ Looking for best way to change 10.87.167.115 to 144.217.33.224 (static/public IP). Prefer doing this in a way where communication between host/container + container/container works without adding iptables rules, which become complex to manage with many containers. Thanks. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] LXD - auto mount home directories
Greetings all, Looking over the email archives, I could not find a 100% answer. I would like to setup LDAP with auto-mount home directories on our Ubuntu containers (servers running LXD 2.0.2 and beyond). I found this thread: https://github.com/lxc/lxd/issues/1826 but did not see a final answer. I also found this: https://github.com/lxc/lxd/issues/2005 Just need final clarification. Thanks. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] lxc 2.0: command get_cgroup failed for 'dom1': Permission denied
Hi folks, since lxc 2.0 my monitoring scripts return error messages about running system containers, e.g.: % lxc-ls -P /data1/lxc --fancy jerry1 lxc-ls: commands.c: lxc_cmd_get_cgroup_path: 468 command get_cgroup failed for 'jerry1': Permission denied lxc-ls: commands.c: lxc_cmd_get_cgroup_path: 468 command get_cgroup failed for 'jerry1': Permission denied lxc-ls: commands.c: lxc_cmd_get_cgroup_path: 468 command get_cgroup failed for 'jerry1': Permission denied lxc-ls: commands.c: lxc_cmd_get_cgroup_path: 468 command get_cgroup failed for 'jerry1': Permission denied NAME STATE AUTOSTART GROUPS IPV4 IPV6 jerry1 - 0 auto -- Using strace the "permission denied" is not shown, but the output of lxc-ls is still broken. This is pretty painful. I wouldn't like to do monitoring with root, if it can be avoided. Plattform is Jessie, lxc 2.0.4. No systemd. Every helpful comment is highly appreciated Harri ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
