You are not logged in.
I have a Docker container called "some-mysql" which is an instance of the "mysql" image. I've been reliably using this container for a very long time now, so I'm surprised to see that starting it now produces this error message:
```
Error response from daemon: failed to set up container networking: failed to create endpoint some-mysql on network bridge: failed to add the host (vethe68cec0) <=> sandbox (vethb65076b) pair interfaces: operation not supported
Error: failed to start containers: some-mysql
```
There are two things I remember doing that could have caused the issue. The first is I recently updated my system. The second is several days ago I had to reconfigure the subnet Docker was using because the Porter airline's in flight wifi uses the same subnet as Docker. This involved removing a `br-*` network, creating /etc/docker/daemon.json with the necessary configuration, and restarting Docker. I have since removed the `daemon.json` file and restarted my laptop.
I forgot to restart - or rather I could have sworn I did an update before a recent reboot, but I must have done it after because the kernel updated and the modules weren't on disk anymore
Last edited by kerneldeimos (2025-08-06 19:48:36)
Offline
My hot take is kernel-modules-hook should be in base
Offline