<div dir="ltr"><div dir="ltr">On Mon, May 27, 2019 at 8:11 PM Saint Michael <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small">I thought I did start the containers as privileged:</div><div style="font-size:small"><br></div><div style="font-size:small">lxc.include = /usr/share/lxc/config/ubuntu.common.conf<br>lxc.mount.auto=<br>lxc.mount.auto=proc:rw sys:rw cgroup:rw<br>lxc.apparmor.profile=unconfined<br>lxc.tty.max = 10<br>lxc.pty.max = 1024<br>lxc.cgroup.devices.allow = c 1:3 rwm<br>lxc.cgroup.devices.allow = c 1:5 rwm<br>lxc.cgroup.devices.allow = c 5:1 rwm<br>lxc.cgroup.devices.allow = c 5:0 rwm<br>lxc.cgroup.devices.allow = c 4:0 rwm<br>lxc.cgroup.devices.allow = c 4:1 rwm<br>lxc.cgroup.devices.allow = c 1:9 rwm<br>lxc.cgroup.devices.allow = c 1:8 rwm<br>lxc.cgroup.devices.allow = c 136:* rwm<br>lxc.cgroup.devices.allow = c 5:2 rwm<br>lxc.cgroup.devices.allow = c 254:0 rwm<br>lxc.cgroup.devices.allow = c 10:137 rwm # loop-control<br>lxc.cgroup.devices.allow = b 7:* rwm    # loop*<br>lxc.cgroup.devices.allow = c 10:229 rwm #fuse<br>lxc.cgroup.devices.allow = c 10:200 rwm #docker<br>lxc.cgroup.devices.allow= a<br>lxc.cap.drop=<br>lxc.cgroup.devices.deny=<br>lxc.autodev= 1<br>lxc.hook.autodev = sh -c 'mknod ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229'<br></div></div></blockquote><div><br></div><div><br></div><div>Following Stephane's suggestion works on my test vm. You didn't do so, thus it didn't work.</div><br>###<br># Distribution configuration<br>lxc.include = /usr/share/lxc/config/common.conf<br>lxc.arch = x86_64<br><br># Container specific configuration<br>lxc.rootfs.path = dir:/var/lib/lxc/c7-ul/rootfs<br><a href="http://lxc.uts.name">lxc.uts.name</a> = c7-ul<br><br>lxc.net.0.type = none<br>lxc.mount.auto=<br>lxc.mount.auto=proc:rw sys:rw cgroup:rw<br>lxc.apparmor.profile=unconfined<br>###<br><br>###</div>c7-ul / # sysctl --system<br>* Applying /usr/lib/sysctl.d/00-system.conf ...<br>* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...<br>kernel.yama.ptrace_scope = 0<br>* Applying /usr/lib/sysctl.d/50-default.conf ...<br>kernel.sysrq = 16<br>kernel.core_uses_pid = 1<br>net.ipv4.conf.default.rp_filter = 1<br>net.ipv4.conf.all.rp_filter = 1<br>net.ipv4.conf.default.accept_source_route = 0<br>net.ipv4.conf.all.accept_source_route = 0<br>net.ipv4.conf.default.promote_secondaries = 1<br>net.ipv4.conf.all.promote_secondaries = 1<br>fs.protected_hardlinks = 1<br>fs.protected_symlinks = 1<br>* Applying /etc/sysctl.d/99-sysctl.conf ...<br>* Applying /etc/sysctl.d/net.conf ...<br>net.core.rmem_max = 67108864<br>net.core.wmem_max = 33554432<br>net.core.rmem_default = 31457280<br>net.core.wmem_default = 31457280<br>* Applying /etc/sysctl.conf ...<br><div class="gmail_quote"><br></div>c7-ul / # cat /proc/sys/net/core/rmem_max <br>67108864<br><div class="gmail_quote">###<br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br>Of course as warned earlier, host networking brings along some quirks. For instance:<br>- host and container can't have services run on the same port (e.g. if you want sshd on both host and container, you need to change the listening port for one of them)<br>- do not configure networking on the container (ONBOOT=no should be enough on your container's eth confi)<br>- absolutely do not run "reboot", "init 6", or "poweroff" on the container. At the very least, it will cause hosts's eth0 to go down. "reboot -f" on the container should work nicely though.</div><div class="gmail_quote"><br></div><div class="gmail_quote">-- </div><div class="gmail_quote">Fajar</div></div>