Yeah, it shouldn’t have any problem mounting, especially since there’s no network shares (until explicitly started after boot), and it’s running on a nvme here. I notice it says
I don’t know if this is a coincidence but here I found this line " overlay Overlay networks connect multiple Docker daemons together." Maybe it’s something to do with a network which brings me to
Sometimes I get this error that hangs shutdowns:
[FAILED] Failed to start Network Manager Wait Online.
^@^@^@^@^@^@^@^@^@^@^@^@
Broadcast message from root@[computer name] on pts/2
The system will power off now!
I thought maybe just a delay for things to get going could help so I added this line below just to throw in a 30s delay
ExecStartPre=/bin/sleep 30
unfortunately the issue still happened, gotta figure out the network manager thing.
I ran
$ nmcli device status
DEVICE TYPE STATE CONNECTION
enp5s0 ethernet connected Wired connection 1
wlan0 wifi connected [snip]
tap-easytether tun connecting (getting IP configuration) EasyTether
tailscale0 tun connected (externally) tailscale0
br-3217fc5f7820 bridge connected (externally) br-3217fc5f7820
br-3fa7f96300fe bridge connected (externally) br-3fa7f96300fe
br-45797add1204 bridge connected (externally) br-45797add1204
br-4e28caf142a4 bridge connected (externally) br-4e28caf142a4
br-5f0446d2d512 bridge connected (externally) br-5f0446d2d512
br-5fb5e76e20cd bridge connected (externally) br-5fb5e76e20cd
br-cfe21c979aa4 bridge connected (externally) br-cfe21c979aa4
lo loopback connected (externally) lo
br-2b5e4fd87ba9 bridge connected (externally) br-2b5e4fd87ba9
br-966b216a8f73 bridge connected (externally) br-966b216a8f73
br-987516d099b6 bridge connected (externally) br-987516d099b6
docker0 bridge connected (externally) docker0
virbr0 bridge connected (externally) virbr0
p2p-dev-wlan0 wifi-p2p disconnected --
veth030b893 ethernet unmanaged --
veth06d9763 ethernet unmanaged --
veth071cc02 ethernet unmanaged --
veth0758f9f ethernet unmanaged --
veth07e1c95 ethernet unmanaged --
veth0af310c ethernet unmanaged --
veth145ea09 ethernet unmanaged --
veth1ccbcc3 ethernet unmanaged --
veth1eb409f ethernet unmanaged --
veth2205a74 ethernet unmanaged --
veth29d40c1 ethernet unmanaged --
veth324e72a ethernet unmanaged --
veth33a78c0 ethernet unmanaged --
veth37afa23 ethernet unmanaged --
veth39bf091 ethernet unmanaged --
veth433bc3a ethernet unmanaged --
veth4887070 ethernet unmanaged --
veth59c0893 ethernet unmanaged --
veth5ca8d12 ethernet unmanaged --
veth664c359 ethernet unmanaged --
veth69d22ac ethernet unmanaged --
veth7a25f7f ethernet unmanaged --
veth81a1d5c ethernet unmanaged --
veth85b6eea ethernet unmanaged --
veth8774839 ethernet unmanaged --
veth88f4508 ethernet unmanaged --
veth8bc5f50 ethernet unmanaged --
veth913d44c ethernet unmanaged --
veth9772d9a ethernet unmanaged --
veth999ae4c ethernet unmanaged --
vethab7ceaf ethernet unmanaged --
vethabe9371 ethernet unmanaged --
vethb0d330f ethernet unmanaged --
vethb151bc6 ethernet unmanaged --
vethb32159e ethernet unmanaged --
vethc7788ff ethernet unmanaged --
vethccadf9a ethernet unmanaged --
vethd5962bc ethernet unmanaged --
vethd59d9af ethernet unmanaged --
vethd82b912 ethernet unmanaged --
vethd834062 ethernet unmanaged --
vethe228ea3 ethernet unmanaged --
vethe2a65b9 ethernet unmanaged --
vethe61f6fd ethernet unmanaged --
vethe761375 ethernet unmanaged --
vethef0d8b4 ethernet unmanaged --
vethf9402bc ethernet unmanaged --
vethf962927 ethernet unmanaged --
vethfa8c262 ethernet unmanaged --
vethfb6e450 ethernet unmanaged --
vethfc2a502 ethernet unmanaged --
should I unmanage some of these you think like in this article? I’m worried about breaking docker networking lol