I must admit that I have neglected the system…
After I could only log in to the console because /dev/root of my umbrella was full due to a /var/log/messages spammed by veth devices (I fixed that in a makeshift way) I now ask myself where the spam comes from - is there something wrong with the network config of the Docker containers?
From the log:
May 10 15:22:39 umbrel kernel: [ 3512.908234] veth69f28d8: renamed from eth0
May 10 15:22:39 umbrel kernel: [ 3512.973348] br-c5bf3a7d5890: port 10(veth1ed278a) entered disabled state
May 10 15:22:39 umbrel kernel: [ 3512.975475] device veth1ed278a left promiscuous mode
May 10 15:22:39 umbrel kernel: [ 3512.975489] br-c5bf3a7d5890: port 10(veth1ed278a) entered disabled state
This affects several more veth devices. How do I fix this?
Update: It seems it is the bitcoind docker image (message spamming stopped after I stopped the container, but I still don’t know why and how to fix it