moby: Error response from daemon: failed to create endpoint (...) on network bridge: failed to add the host (veth1d85371) <=> sandbox (vethbc264f6) pair interfaces: operation not supported.

I don’t see any problem there. I’ve just left the comment for the ones using Arch Linux so they know a reboot is needed after updating the kernel.

Thanks for your clarification @thaJeztah.

In my case, the error appears every time I update my Linux kernel. It disappears when I restart the computer.

I am using Arch Linux.

Update:

An alternative is to downgrade the kernel if restart isn’t feasible at the moment.

sudo pacman -U /var/cache/pacman/pkg/linux-$(uname -r | sed 's/-ARCH//')-x86_64.pkg.tar.xz

Credits to @Nowaker . See comment below

@whoan For Arch Linux, after you update the kernel, the old kernel modules will be all deleted (replaced with new version kernel modules) automatically. So if you didn’t restart computer, you will be running old kernel without matched kernel modules. Most docker commands will load kernel modules (if they haven’t been loaded yet), but your old kernel can’t find its modules any more. That is why the error appears every time you update your Linux kernel, and disappears after you restart the computer.

Kernel modules directory is in /lib/modules/. Next time before you update kernel, backup the old kernel modules directory. After update, restore the old kernel modules directory, then you won’t see this error even if you don’t restart computer.

https://stackoverflow.com/questions/69780128/docker-error-response-from-daemon-failed-to-create-endpoint-priceless-noether

The vent kernel module is not installed. do: sudo apt install linux-modules-extra-raspi

I should add for other Arch users that the reboot in my case was due to a system upgrade the same day. Seems like docker can’t establish connection if you upgraded arch without rebooting.

Seems like Linux copied that trick from Windows

@whoan An alternative is to downgrade the kernel if restart isn’t feasible at the moment. I’d be great if you could edit your comment so that all the knowledge is in one place. Thanks 😃

sudo pacman -U /var/cache/pacman/pkg/linux-$(uname -r | sed 's/-ARCH//)'-x86_64.pkg.tar.xz

I was having this issue because I was running a custom built kernel without the Virtual ethernet pair device option. So in case you have a custom kernel, make to enable that option before running make. You’ll find it under:

Device Drivers -> Network device support -> Network core driver support

Putting this here because this seems to be the first result on Google for this error. Hope it helps!

Looks like you’re running a non-standard kernel for Ubuntu 14.04. Ubuntu 14.04 ships with Kernel 3.13. Can you try with a standard kernel? It’s possible your kernel is missing modules that are required for docker to function properly; you can try running this script to see what’s missing; https://github.com/docker/docker/blob/master/contrib/check-config.sh

Same kind of trouble with my Raspberry PI. Restart solved the problem.

Who knew? The solution was to turn it off and back on again.

@Nowaker thanks! Minor typo fix for future searchers: sudo pacman -U /var/cache/pacman/pkg/linux-$(uname -r | sed 's/-ARCH//')-x86_64.pkg.tar.xz (note the swapped positions of the final single quote and parenthesis)

Thanks @Nowaker for your contribution. I added it to my previous comment as suggested.

Thank you so much @briangu , you just saved me another 5h of searching for answers !

@tomas , Thanks for your answer above, it solved my problem. Thanks a lot.

I have the same error, but did not work after reboot. So I rm all images and containsers with command docker image rm and docker rm to delete. Then docker works fine.

Just had this issue popping up after upgrading Arch Linux to kernel 6.0.8

$ uname -a
Linux e595 6.0.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Nov 2022 21:14:24 +0000 x86_64 GNU/Linux

Best tip is to update the bootloader (e.g. sudo grub-mkconfig -o /boot/grub/grub.cfg for grub users, or sudo bootctl update for systemd-boot and then reboot.

Hope this helps.

@coderj001 Have you tried this? https://github.com/moby/moby/issues/27426#issuecomment-278524987

In my case, the error appears every time I update my Linux kernel. It disappears when I restart the computer.

I am using Arch Linux.

Update:

An alternative is to downgrade the kernel if restart isn’t feasible at the moment.

sudo pacman -U /var/cache/pacman/pkg/linux-$(uname -r | sed 's/-ARCH//')-x86_64.pkg.tar.xz

Credits to @Nowaker . See comment below

Thanks Man it worked. I had just updated my kernel so that’s why it showing me error.