Bridge creating over and over new interfaces

Docker Engine General
1

Hello, I noticed this strange behavior in my client machine, the problem was, my reverse proxy was restarting over and over, we use docker dns to redirect the request to the appropriate container, the reverse proxy was restarting for unknown reason until i investigate, looking the docker logs in journalctl i found this:

`Sep 18 18:20:50 do-vm systemd-networkd[13678]: vethb1714ae: Link UP`
`Sep 18 18:20:50 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered blocking state`
`Sep 18 18:20:50 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered disabled state`
`Sep 18 18:20:50 do-vm kernel: device vethb1714ae entered promiscuous mode`
`Sep 18 18:20:50 do-vm kernel: IPv6: ADDRCONF(NETDEV_UP): vethb1714ae: link is not ready`
`Sep 18 18:20:50 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered blocking state`
`Sep 18 18:20:50 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered forwarding state`
`Sep 18 18:20:50 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered disabled state`
`Sep 18 18:20:50 do-vm networkd-dispatcher[1292]: WARNING:Unknown index 1274 seen, reloading interface list`
`Sep 18 18:20:50 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:20:50 do-vm systemd-udevd[23459]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:20:50 do-vm systemd-udevd[23459]: Could not generate persistent MAC address for vethbf4a753: No such file or directory`
`Sep 18 18:20:50 do-vm systemd-udevd[23460]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:20:50 do-vm systemd-udevd[23460]: Could not generate persistent MAC address for vethb1714ae: No such file or directory`
``` Sep 18 18:20:51 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.208749850Z” level=info msg=“shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.208876028Z” level=warning msg=“cleaning up after shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc namespace=moby`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.208911353Z” level=info msg=“cleaning up dead shim”`
`Sep 18 18:20:51 do-vm dockerd[1098]: time=“2025-09-18T18:20:51.208791095Z” level=info msg=“ignoring event” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc module=libcontainerd namespace=moby`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.224146181Z” level=warning msg="cleanup warnings time="2025-09-18T18:20:51Z" level=info msg="starting signal loop" namespace=moby pid=23654 runtime=`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.251163856Z” level=info msg=“loading plugin "io.containerd.event.v1.publisher"…” runtime=io.containerd.runc.v2 type=io.containerd.event.v1`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.251289123Z” level=info msg=“loading plugin "io.containerd.internal.v1.shutdown"…” runtime=io.containerd.runc.v2 type=io.containerd.internal.v1`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.251331984Z” level=info msg=“loading plugin "io.containerd.ttrpc.v1.task"…” runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1`
`Sep 18 18:20:51 do-vm containerd[31031]: time=“2025-09-18T18:20:51.251904407Z” level=info msg=“starting signal loop” namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/e86104757018afeac4a7091791e422`
`Sep 18 18:20:51 do-vm sshd[23455]: Connection closed by authenticating do-vm root 193.32.162.157 port 50446 [preauth]`
`Sep 18 18:20:51 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:20:51 do-vm kernel: eth0: renamed from vethbf4a753`
`Sep 18 18:20:51 do-vm systemd-networkd[13678]: vethb1714ae: Gained carrier`
`Sep 18 18:20:51 do-vm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb1714ae: link becomes ready`
`Sep 18 18:20:51 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered blocking state`
`Sep 18 18:20:51 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered forwarding state`
``` Sep 18 18:20:51 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:20:51 do-vm dockerd[1098]: time=“2025-09-18T18:20:51.942141426Z” level=warning msg=“failed to delete container from containerd” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc error`
`Sep 18 18:20:52 do-vm systemd-networkd[13678]: vethb1714ae: Gained IPv6LL`
`Sep 18 18:20:52 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
``` Sep 18 18:20:52 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:20:53 do-vm dockerd[1098]: time=“2025-09-18T18:20:53.943372818Z” level=error msg=“stream copy error: read /proc/self/fd/80: file already closed”`
`Sep 18 18:20:53 do-vm dockerd[1098]: time=“2025-09-18T18:20:53.943411845Z” level=error msg=“stream copy error: read /proc/self/fd/65: file already closed”`
`Sep 18 18:20:53 do-vm dockerd[1098]: time=“2025-09-18T18:20:53.945087552Z” level=error msg="e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc cleanup: failed to delete container from containerd: cannot d`
`Sep 18 18:20:54 do-vm systemd-networkd[13678]: vethb1714ae: Lost carrier`
`Sep 18 18:20:54 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered disabled state`
`Sep 18 18:20:54 do-vm kernel: vethbf4a753: renamed from eth0`
`Sep 18 18:20:54 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:20:54 do-vm systemd-udevd[23833]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:20:54 do-vm systemd-networkd[13678]: vethb1714ae: Link DOWN`
`Sep 18 18:20:54 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered disabled state`
`Sep 18 18:20:54 do-vm networkd-dispatcher[1292]: WARNING:Unknown index 1273 seen, reloading interface list`
`Sep 18 18:20:54 do-vm kernel: device vethb1714ae left promiscuous mode`
`Sep 18 18:20:54 do-vm kernel: br-04c12470dd51: port 1(vethb1714ae) entered disabled state`
`Sep 18 18:20:54 do-vm systemd-udevd[23833]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:20:54 do-vm systemd-udevd[23833]: link_config: could not get ethtool features for vethbf4a753`
`Sep 18 18:20:54 do-vm systemd-udevd[23833]: Could not set offload features of vethbf4a753: No such device`
`Sep 18 18:20:54 do-vm networkd-dispatcher[1292]: ERROR:Unknown interface index 1273 seen even after reload`
``` Sep 18 18:20:54 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:21:05 do-vm sshd[23735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh rdo-vm= rhost=193.32.162.157  do-vm=root`
`Sep 18 18:21:06 do-vm sshd[23735]: Failed password for root from 193.32.162.157 port 50074 ssh2`
`Sep 18 18:21:53 do-vm systemd-networkd[13678]: veth63a74b4: Link UP`
`Sep 18 18:21:53 do-vm systemd-udevd[23867]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:21:53 do-vm networkd-dispatcher[1292]: WARNING:Unknown index 1276 seen, reloading interface list`
`Sep 18 18:21:53 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered blocking state`
`Sep 18 18:21:53 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered disabled state`
`Sep 18 18:21:53 do-vm kernel: device veth63a74b4 entered promiscuous mode`
`Sep 18 18:21:53 do-vm kernel: IPv6: ADDRCONF(NETDEV_UP): veth63a74b4: link is not ready`
`Sep 18 18:21:53 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered blocking state`
`Sep 18 18:21:53 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered forwarding state`
`Sep 18 18:21:53 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered disabled state`
`Sep 18 18:21:53 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:21:53 do-vm systemd-udevd[23867]: Could not generate persistent MAC address for vethe2c9676: No such file or directory`
`Sep 18 18:21:53 do-vm systemd-udevd[23868]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:21:53 do-vm dockerd[1098]: time=“2025-09-18T18:21:53.953857612Z” level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.`
`Sep 18 18:21:53 do-vm dockerd[1098]: time=“2025-09-18T18:21:53.953952682Z” level=info msg=“IPv6 enabled; Adding default IPv6 external servers: [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]”`
`Sep 18 18:21:53 do-vm systemd-udevd[23868]: Could not generate persistent MAC address for veth63a74b4: No such file or directory`
``` Sep 18 18:21:54 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.256930984Z” level=info msg=“shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.257027026Z” level=warning msg=“cleaning up after shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc namespace=moby`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.257071395Z” level=info msg=“cleaning up dead shim”`
`Sep 18 18:21:54 do-vm dockerd[1098]: time=“2025-09-18T18:21:54.256988955Z” level=info msg=“ignoring event” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc module=libcontainerd namespace=moby`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.272877043Z” level=warning msg="cleanup warnings time="2025-09-18T18:21:54Z" level=info msg="starting signal loop" namespace=moby pid=24070 runtime=`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.298530892Z” level=info msg=“loading plugin "io.containerd.event.v1.publisher"…” runtime=io.containerd.runc.v2 type=io.containerd.event.v1`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.298654958Z” level=info msg=“loading plugin "io.containerd.internal.v1.shutdown"…” runtime=io.containerd.runc.v2 type=io.containerd.internal.v1`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.298691116Z” level=info msg=“loading plugin "io.containerd.ttrpc.v1.task"…” runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1`
`Sep 18 18:21:54 do-vm containerd[31031]: time=“2025-09-18T18:21:54.299073441Z” level=info msg=“starting signal loop” namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/e86104757018afeac4a7091791e422`
`Sep 18 18:21:54 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:21:54 do-vm kernel: eth0: renamed from vethe2c9676`
`Sep 18 18:21:54 do-vm systemd-networkd[13678]: veth63a74b4: Gained carrier`
`Sep 18 18:21:54 do-vm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth63a74b4: link becomes ready`
`Sep 18 18:21:54 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered blocking state`
`Sep 18 18:21:54 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered forwarding state`
``` Sep 18 18:21:54 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:21:54 do-vm dockerd[1098]: time=“2025-09-18T18:21:54.931489385Z” level=warning msg=“failed to delete container from containerd” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc error`
`Sep 18 18:21:56 do-vm systemd-networkd[13678]: veth63a74b4: Gained IPv6LL`
`Sep 18 18:21:56 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
``` Sep 18 18:21:56 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:21:56 do-vm dockerd[1098]: time=“2025-09-18T18:21:56.932170508Z” level=error msg=“stream copy error: read /proc/self/fd/65: file already closed”`
`Sep 18 18:21:56 do-vm dockerd[1098]: time=“2025-09-18T18:21:56.932373711Z” level=error msg=“stream copy error: read /proc/self/fd/80: file already closed”`
`Sep 18 18:21:56 do-vm dockerd[1098]: time=“2025-09-18T18:21:56.934197553Z” level=error msg="e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc cleanup: failed to delete container from containerd: cannot d`
`Sep 18 18:21:57 do-vm systemd-networkd[13678]: veth63a74b4: Lost carrier`
`Sep 18 18:21:57 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:21:57 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered disabled state`
`Sep 18 18:21:57 do-vm kernel: vethe2c9676: renamed from eth0`
`Sep 18 18:21:57 do-vm systemd-udevd[24233]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:21:57 do-vm systemd-networkd[13678]: veth63a74b4: Link DOWN`
`Sep 18 18:21:57 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered disabled state`
`Sep 18 18:21:57 do-vm networkd-dispatcher[1292]: WARNING:Unknown index 1275 seen, reloading interface list`
`Sep 18 18:21:57 do-vm kernel: device veth63a74b4 left promiscuous mode`
`Sep 18 18:21:57 do-vm kernel: br-04c12470dd51: port 1(veth63a74b4) entered disabled state`
`Sep 18 18:21:57 do-vm systemd-udevd[24233]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:21:57 do-vm systemd-udevd[24233]: link_config: could not get ethtool features for vethe2c9676`
`Sep 18 18:21:57 do-vm systemd-udevd[24233]: Could not set offload features of vethe2c9676: No such device`
`Sep 18 18:21:57 do-vm networkd-dispatcher[1292]: ERROR:Unknown interface index 1275 seen even after reload`
``` Sep 18 18:21:57 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:22:56 do-vm systemd-networkd[13678]: vethd4f2d31: Link UP`
`Sep 18 18:22:56 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered blocking state`
`Sep 18 18:22:56 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered disabled state`
`Sep 18 18:22:56 do-vm kernel: device vethd4f2d31 entered promiscuous mode`
`Sep 18 18:22:56 do-vm kernel: IPv6: ADDRCONF(NETDEV_UP): vethd4f2d31: link is not ready`
`Sep 18 18:22:56 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered blocking state`
`Sep 18 18:22:56 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered forwarding state`
`Sep 18 18:22:56 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:22:56 do-vm networkd-dispatcher[1292]: WARNING:Unknown index 1278 seen, reloading interface list`
`Sep 18 18:22:56 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered disabled state`
`Sep 18 18:22:56 do-vm systemd-udevd[24269]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:22:56 do-vm systemd-udevd[24270]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.`
`Sep 18 18:22:56 do-vm systemd-udevd[24270]: Could not generate persistent MAC address for vethd4f2d31: No such file or directory`
`Sep 18 18:22:56 do-vm systemd-udevd[24269]: Could not generate persistent MAC address for vethc58965a: No such file or directory`
`Sep 18 18:22:56 do-vm dockerd[1098]: time=“2025-09-18T18:22:56.943059230Z” level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.`
`Sep 18 18:22:56 do-vm dockerd[1098]: time=“2025-09-18T18:22:56.943138947Z” level=info msg=“IPv6 enabled; Adding default IPv6 external servers: [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]”`
``` Sep 18 18:22:57 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:22:57 do-vm dockerd[1098]: time=“2025-09-18T18:22:57.232663162Z” level=info msg=“ignoring event” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc module=libcontainerd namespace=moby`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.233370767Z” level=info msg=“shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.233566910Z” level=warning msg=“cleaning up after shim disconnected” id=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc namespace=moby`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.233600980Z” level=info msg=“cleaning up dead shim”`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.249941344Z” level=warning msg="cleanup warnings time="2025-09-18T18:22:57Z" level=info msg="starting signal loop" namespace=moby pid=24467 runtime=`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.276855113Z” level=info msg=“loading plugin "io.containerd.event.v1.publisher"…” runtime=io.containerd.runc.v2 type=io.containerd.event.v1`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.277009823Z” level=info msg=“loading plugin "io.containerd.internal.v1.shutdown"…” runtime=io.containerd.runc.v2 type=io.containerd.internal.v1`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.277033849Z” level=info msg=“loading plugin "io.containerd.ttrpc.v1.task"…” runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1`
`Sep 18 18:22:57 do-vm containerd[31031]: time=“2025-09-18T18:22:57.277427775Z” level=info msg=“starting signal loop” namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/e86104757018afeac4a7091791e422`
`Sep 18 18:22:57 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
`Sep 18 18:22:57 do-vm kernel: eth0: renamed from vethc58965a`
`Sep 18 18:22:57 do-vm systemd-networkd[13678]: vethd4f2d31: Gained carrier`
`Sep 18 18:22:57 do-vm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd4f2d31: link becomes ready`
`Sep 18 18:22:57 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered blocking state`
`Sep 18 18:22:57 do-vm kernel: br-04c12470dd51: port 1(vethd4f2d31) entered forwarding state`
``` Sep 18 18:22:57 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:22:57 do-vm dockerd[1098]: time=“2025-09-18T18:22:57.843117316Z” level=warning msg=“failed to delete container from containerd” container=e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc error`
`Sep 18 18:22:58 do-vm systemd-networkd[13678]: vethd4f2d31: Gained IPv6LL`
`Sep 18 18:22:58 do-vm systemd-timesyncd[30351]: Network configuration changed, trying to establish connection.`
``` Sep 18 18:22:59 do-vm systemd-timesyncd[30351]: Synchronized to time server 185.125.190.56:123 (``ntp.ubuntu.com``). ```
`Sep 18 18:22:59 do-vm dockerd[1098]: time=“2025-09-18T18:22:59.843747764Z” level=error msg=“stream copy error: read /proc/self/fd/65: file already closed”`
`Sep 18 18:22:59 do-vm dockerd[1098]: time=“2025-09-18T18:22:59.843880085Z” level=error msg=“stream copy error: read /proc/self/fd/80: file already closed”`
`Sep 18 18:22:59 do-vm dockerd[1098]: time=“2025-09-18T18:22:59.845684965Z” level=error msg="e86104757018afeac4a7091791e4229737174519eae8287197c456b152e0d8cc cleanup: failed to delete container from containerd: cannot d`
`Sep 18 18:22:59 do-vm systemd-networkd[13678]: vethd4f2d31: Lost carrier`

I reproduced this error by setting down the bridge my docker network uses. I have more than 10 containers running in the same network, we dont use any other network in the containers, just one. The problem was the bridge repeatedly recreated virtual interfaces over and over, causing failure in the dns resolution in my reverse proxy, i dont know why docker had this behavior, i know when this error happend, the machine was fine, no problems whatsoever, i hope someone can help me mitigate this problem, if updatind docker is the best way… etc

Infos:

docker info
Client: Docker Engine - Community
Version:    24.0.2
Context:    default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version:  v0.10.5
Path:     /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version:  v2.18.1
Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 14
Running: 14
Paused: 0
Stopped: 0
Images: 15
Server Version: 24.0.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version: v1.1.7-0-g860f061
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
Kernel Version: 4.15.0-213-generic
Operating System: Ubuntu 18.04.6 LTS
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.41GiB
Name: name
ID: 7fe21135-69c9-4178-9d7d-3974f13a7bcc
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: isisdemo
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

docker version
Client: Docker Engine - Community
Version:           24.0.2
API version:       1.43
Go version:        go1.20.4
Git commit:        cb74dfc
Built:             Thu May 25 21:52:13 2023
OS/Arch:           linux/amd64
Context:           default

Server: Docker Engine - Community
Engine:
Version:          24.0.2
API version:      1.43 (minimum version 1.12)
Go version:       go1.20.4
Git commit:       659604f
Built:            Thu May 25 21:52:13 2023
OS/Arch:          linux/amd64
Experimental:     true
containerd:
Version:          1.6.21
GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
runc:
Version:          1.1.7
GitCommit:        v1.1.7-0-g860f061
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

ii  docker-buildx-plugin      0.10.5-1\~ubuntu.18.04\~bionic   amd64        Docker Buildx cli plugin.
ii  docker-ce                 5:24.0.2-1\~ubuntu.18.04\~bionic amd64        Docker: the open-source application container engine
ii  docker-ce-cli             5:24.0.2-1\~ubuntu.18.04\~bionic amd64        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras 5:24.0.2-1\~ubuntu.18.04\~bionic amd64        Rootless support for Docker.
ii  docker-compose-plugin     2.18.1-1\~ubuntu.18.04\~bionic   amd64        Docker Compose (V2) plugin for the Docker CLI.

snap list docker
error: no matching snaps installed
2

I am not sure if its worth fixing anything on a setup where the os (Ubuntu 18.04) reached end of life on 31 May 2023, and the docker engine (24.0.2) reached eol on 08 June 2024.

While there is an option to buy an Ubuntu Pro subscription, there is no such thing for the docker engine.

Are you sure your containers are running stable, and don’t exit for a reason caused by whatever happens inside the container?

3

im aware the end of suport, and im sure the container was ok until this problem, i just want to know if updating can fix this

4

Just because someone says it might not be wotth fixing it, it doesn’t mean you wouldnt get some ideas, but for that some more information would be needed and @meyay even asked a question, which is an actually important question.

I understand that the containers worked before, but we don’t know enough about your environment to rule out changes in that environment that you don’t know of.

I rarely have to see those kind of logs you shared, so I’m not sure what I could say based on that. I think those I recognize could be normal when a container is crashing or recreated, but it doesn’t show why it happens.

I see deleting containers in the logs, but when you just restart a container, it would not be deleted, so there must be something that deletes the containers. Are you running Docker Swarm or just simple Docker Compose?

Is there any automation? In many cases people find scripts they didn’t remember or were deployed by someone else. Or services that were installed by accident, maybe ven as a dependency of something else. Even a restart or reboot can cause problems if some services are running only then and cannot reach some external sources that werealready deleted or changed.

5

The environment: we use Docker Compose and always restart, which is why the container was being recreated several times. Before these restarts, the environment was fine, with all containers running. I am 100% sure that there was no script that could have caused this. Could this virtual network log be linked to the container restart? On my machine, when there are no containers running, there is no veth, but when there is one, a veth is created. Could these veth creations be linked to the restarts? Since there is an “always restart” policy, I think I was thinking about it the wrong way.

6

Restart could cause the veth logs, but not the “failed to delete container from containerd” message.

So unless it was an intentional container deletion, there is something more than just restarting. I could not reproduce those logs now when I tried to delete a container, stop a container, restart a container or even restart the docker daemon and containerd as well.

7

I am not sure about that it’s the soluation of my following doubt. What’s the status of the usage of memory cache ?Alternatively, insufficient memory or cache might have caused the container to stop unexpectedly.

8

That would be visible in the daemon logs as OOM kill.

9

Haha~ That’s like a ghost!

10

I am not really sure what you mean by that. Can you elaborate what you mean?

If the restart policy is set to no, chances are high that it can be even seen on the exit code of the container. If the container is gone it should be still visible in the logs.

Test it yourself:

# create a container that ooms
docker run -ti --name oomk --memory=6m -e POSTGRES_PASSWORD=password  postgres

## detect oom kill

# if container still exists
docker inspect --format '{{json .State.OOMKilled}}' oomk

# based on syslog file
grep "oom" /var/log/syslog

# based on systemd syslogs
journalctl  --since "30 minutes ago" --grep "oom"

# cleanup exited contaiener
docker rm oomk
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.