Upgraded to 6.12.8 - frequent crashes

Feb 23 02:23:05 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Feb 23 02:23:05 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Feb 23 02:23:05 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Change to ipvlan and reboot, if it still crashes post a new syslog

That's odd. I remember I switched network type to 'ipvlan'.

 

I restarted the server and noticed 'Docker Service failed to start.' error message when I browsed to 'Docker' tab. I changed network from 'macvlan' to 'ipvlan' and rebooted the server. But same error message. 

I know Docker image is corrupted. I deleted vdisk file and created again with 'ipvlan' network type.

 

root@Tower:~# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
9dd32ab44a95   br0       ipvlan    local
7bcb1926472d   bridge    bridge    local
53da3ff4205d   host      host      local
0f34678ea99b   none      null      local

 

Before I manually add containers (via Apps -> Previous Apps), is there anything specific I need to keep in mind?

Also, yesterday whenever I tweaked something in a container settings, the page took forever to load.

 

Here are the network types from yesterday. I have no idea why there are two networks for mosquitto.

 

root@Tower:~# docker network ls
NETWORK ID     NAME                               DRIVER    SCOPE
af663fcb60e1   br0                                macvlan   local
e5ba80db4137   bridge                             bridge    local
8a2b4457487a   host                               host      local
b20c276505ed   mosquitto_docker-compose_default   bridge    local
49e8289e979d   mosquitto_docker_compose_default   bridge    local
4ff659169f3c   none                               null      local
5c6c047a2ff6   utils_default                      bridge    local

 

Edited February 23 by stlrox
Addl info reg. networks

7 minutes ago, stlrox said:

. I have no idea why there are two networks for mosquitto.

Can't help with that, but it does confirm macvlan was enabled with bridging, that is the dangerous configuration, you can use ipvlan, or macvlan but with bridging disabled.

How did you figure out the following from 'docker network ls' command? Just curious
"it does confirm macvlan was enabled with bridging"

I've installed a few containers (3 - host, 3 - bridge). I will hold off on adding more until tomorrow. 🤞

15 hours ago, stlrox said:

How did you figure out the following from 'docker network ls' command?

 

17 hours ago, stlrox said:

NETWORK ID     NAME                               DRIVER    SCOPE
af663fcb60e1   br0                                macvlan   local

 

It's been more than one week with 11 containers running. I don't know why ipvlan didn't work before, but after making the change, system is stable.
 

root@Tower:/mnt/user/appdata# dnetworks
NETWORK ID     NAME                DRIVER    SCOPE
9dd32ab44a95   br0                 ipvlan    local
7bcb1926472d   bridge              bridge    local
53da3ff4205d   host                host      local
92ef905a9981   mosquitto_default   bridge    local
0f34678ea99b   none                null      local
root@Tower:/mnt/user/appdata#

root@Tower:/mnt/user/appdata# docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          11        11        4.929GB   7.335MB (0%)
Containers      11        11        103.8MB   0B (0%)
Local Volumes   3         1         0B        0B
Build Cache     0         0         0B        0B

 

Changed Status to Solved