It seems this bug has been fixed in
https://github.com/moby/libnetwork/pull/1502, which is available since
Docker 1.13. Therefore, this has been fixed since bionic.
I tried to reproduce the issue with
$ lxc launch ubuntu-daily:jammy -c security.nesting=true docker-j
$ lxc exec docker-j -- bash
#
Same issue on debian 8.6 (jessie) with kernel proxmox 4.4.24-1-pve under lxc
(2).
In this kernel, modules "br_netfilter" and "bridge" compiled with kernel.
# docker network create -d overlay --subnet=192.168.0.0/16
--gateway=192.168.0.1 --ip-range=192.168.1.0/24 multihost-network1
# docker
This was discussed with the LXD team here:
https://github.com/lxc/lxd/issues/2321
This feels like a Docker bug to us, where it's attempting to load kernel
modules regardless of them already being loaded, then failing because
modprobe in a container can't see the .ko
** Bug watch added: LXD bug
** Changed in: docker.io (Ubuntu)
Status: New => Triaged
** Changed in: docker.io (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618283
Title:
