I upgraded Docker from 29.3.1 to 29.4.0 and after restarting the OS I found Docker could not start any of the Bitwarden containers:
Apr 13 07:55:28 BITWARDEN dockerd[5862]: time="2026-04-13T07:55:28.028753805-05:00" level=info msg="Restoring containers: start."
Apr 13 07:55:28 BITWARDEN dockerd[5862]: time="2026-04-13T07:55:28.143472992-05:00" level=warning msg="error locating sandbox id bdfb13a5b0fd6a2ed47b51e8b2146ee8096678ff69764959b72604b2e1f62658: sandbox bdfb13a5b
0fd6a2ed47b51e8b2146ee8096678ff69764959b72604b2e1f62658 not found"
Apr 13 07:55:28 BITWARDEN dockerd[5862]: time="2026-04-13T07:55:28.143504019-05:00" level=warning msg="error locating sandbox id d5c3af0519a6c1c1e02f486e8fbc473d1fcd23e39da0b4817d19a76ae854deda: sandbox d5c3af051
9a6c1c1e02f486e8fbc473d1fcd23e39da0b4817d19a76ae854deda not found"
[…]
Apr 13 07:55:29 BITWARDEN dockerd[5862]: time="2026-04-13T07:55:29.897152902-05:00" level=error msg="failed to start container" container=07dfcd501b79f7ebb5c3a8fad897ad16052c098badb17986ad36204fa2a90e40 error="failed to set up container networking: failed to create endpoint bitwarden-web on network docker_default: network 144c741c6cfa69c9934a81180181a35480c3b61b5898880895559d2dea6bfa5a does not exist"
[…]
I verified the network docker_default does indeed exist with that particular network ID. I suspect recreating the containers will fix the problem because I am able to start brand new containers. What is the recommended procedure for doing this? I know how to remove the containers, but I don’t know the preferred method for recreating them. Is it just a matter of running bitwarden.sh start?