Network problem after a couple of restarts

:warning: IMPORTANT, please fill the questions

We assume you are using Bitnami to deploy your application.

  • Which version of the application are you using?:
    BITNAMI LMS POWERED BY MOODLE™ LMS CONTAINERS

  • Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, …) or VM (VMDK, VBOX):
    Docker 3.10.1-0

  • Have you installed any plugin or modified any configuration file?:
    yes

  • Describe here your question/suggestion/issue (expected and actual results):
    I downloaded the docker-compose file and modified it a little.
    I have it running on 2 local machines with Ubuntu 20.4.2 LTS without any problems.
    When I deploy it on another virtual machine, running Ubuntu 20.4.2 as well (created with hyper-v)
    I run into the a strange network problem. The problem only arrises after a few docker-compose up/down commands
    All of a sudden I cannot start it anymore. While mariadb stats fine, Moodle cannot connect to the mariadb anymore and exits.

  • Steps to reproduce the issue (if relevant):
    run docker-compose up and docker-compose down multiple times

  • Copy the apache log (if relevant):
    Here’s some lines from my syslog

Feb 24 14:33:35 in4msrvdocker2 systemd-networkd[630]: vethb983adf: Gained IPv6LL
Feb 24 14:33:35 in4msrvdocker2 systemd-networkd[630]: br-4302efa29260: Gained IPv6LL
Feb 24 14:33:36 in4msrvdocker2 systemd-networkd[630]: veth9e8fad4: Gained IPv6LL
Feb 24 14:33:42 in4msrvdocker2 dockerd[825]: time="2021-02-24T14:33:42.791629824Z" level=info msg="ignoring event" container=bac63b3f5daf6a27a5df707cd708fbe10adbe458cba8d0702091a43c8730d23d module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Feb 24 14:33:42 in4msrvdocker2 containerd[710]: time="2021-02-24T14:33:42.792814728Z" level=info msg="shim disconnected" id=bac63b3f5daf6a27a5df707cd708fbe10adbe458cba8d0702091a43c8730d23d
Feb 24 14:33:42 in4msrvdocker2 systemd-networkd[630]: veth9e8fad4: Lost carrier
Feb 24 14:33:42 in4msrvdocker2 kernel: [87892.397305] br-4302efa29260: port 2(veth9e8fad4) entered disabled state
Feb 24 14:33:42 in4msrvdocker2 kernel: [87892.399986] vethd8136e3: renamed from eth0
Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[665]: WARNING:Unknown index 40 seen, reloading interface list
Feb 24 14:33:42 in4msrvdocker2 systemd-networkd[630]: veth9e8fad4: Link DOWN
Feb 24 14:33:42 in4msrvdocker2 kernel: [87892.418768] br-4302efa29260: port 2(veth9e8fad4) entered disabled state
Feb 24 14:33:42 in4msrvdocker2 systemd-networkd[630]: rtnl: received neighbor for link '41' we don't know about, ignoring.
Feb 24 14:33:42 in4msrvdocker2 kernel: [87892.422166] device veth9e8fad4 left promiscuous mode
Feb 24 14:33:42 in4msrvdocker2 kernel: [87892.422170] br-4302efa29260: port 2(veth9e8fad4) entered disabled state
Feb 24 14:33:42 in4msrvdocker2 systemd-networkd[630]: rtnl: received neighbor for link '41' we don't know about, ignoring.
Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[665]: ERROR:Unknown interface index 40 seen even after reload
Feb 24 14:33:42 in4msrvdocker2 systemd[11086]: run-docker-netns-ad464837d2fe.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd[1]: run-docker-netns-ad464837d2fe.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd[11086]: var-lib-docker-containers-bac63b3f5daf6a27a5df707cd708fbe10adbe458cba8d0702091a43c8730d23d-mounts-shm.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd[1]: var-lib-docker-containers-bac63b3f5daf6a27a5df707cd708fbe10adbe458cba8d0702091a43c8730d23d-mounts-shm.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd[11086]: var-lib-docker-overlay2-691e4d21839a8af2971851be89409dd5b3ebc47afc779c1162ec0017da150ab4-merged.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd[1]: var-lib-docker-overlay2-691e4d21839a8af2971851be89409dd5b3ebc47afc779c1162ec0017da150ab4-merged.mount: Succeeded.
Feb 24 14:33:42 in4msrvdocker2 systemd-udevd[11899]: vethd8136e3: Failed to get link config: No such device
Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[11912]: #033[0;1;31mInterface "veth9e8fad4" not found.#033[0m
Feb 24 14:33:42 in4msrvdocker2 systemd[1]: networkd-dispatcher.service: Got notification message from PID 11912, but reception only permitted for main PID 665Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[665]: ERROR:Failed to get interface "veth9e8fad4" status: Command '['/bin/networkctl', 'status', '--no-pager', '--no-legend', '--', 'veth9e8fad4']' returned non-zero exit status 1.
Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[665]: WARNING:Unknown index 40 seen, reloading interface list
Feb 24 14:33:42 in4msrvdocker2 networkd-dispatcher[665]: ERROR:Unknown interface index 40 seen even after reload
Feb 24 14:33:42 in4msrvdocker2 systemd-udevd[11892]: vethd8136e3: Failed to get link config: No such device

Here’s the output of ipp add show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:01:0b:12 brd ff:ff:ff:ff:ff:ff
    inet 10.1.3.100/24 brd 10.1.3.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe01:b12/64 scope link
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:c6:91:71:6e brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:c6ff:fe91:716e/64 scope link
       valid_lft forever preferred_lft forever
32: br-9cd330a913b7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:27:4b:2d:b7 brd ff:ff:ff:ff:ff:ff
    inet 172.21.0.1/16 brd 172.21.255.255 scope global br-9cd330a913b7
       valid_lft forever preferred_lft forever
    inet6 fe80::42:27ff:fe4b:2db7/64 scope link
       valid_lft forever preferred_lft forever
36: veth9ebdca1@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9cd330a913b7 state UP group default
    link/ether a6:3e:ce:0e:7a:6b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::a43e:ceff:fe0e:7a6b/64 scope link
       valid_lft forever preferred_lft forever
37: br-4302efa29260: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:f6:de:d4:51 brd ff:ff:ff:ff:ff:ff
    inet 172.22.0.1/16 brd 172.22.255.255 scope global br-4302efa29260
       valid_lft forever preferred_lft forever
    inet6 fe80::42:f6ff:fede:d451/64 scope link
       valid_lft forever preferred_lft forever
39: vethb983adf@if38: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-4302efa29260 state UP group default
    link/ether 6e:93:5a:86:8c:da brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::6c93:5aff:fe86:8cda/64 scope link
       valid_lft forever preferred_lft forever

Thank you very much for your support

Hello @in4moodle,

We provide technical support for our containers in our Github repositories. Our team is actively monitoring them and will be glad to help you there, usually within a business day, and the whole community will benefit from your contribution. Could you please post your question by creating a new issue in the testlink repo?

https://github.com/bitnami/bitnami-docker-moodle/issues

Thank you for your understanding!