Docker: failed to add the pair interfaces (operation not supported)

Question

After installing Docker, I am getting an error when I try to run the Hello World example:

Error response from daemon: Cannot start container 4145d0fccd96b904e4ab4413735f1129b8765429bad5be71dc8d5f4c0760666d:
failed to create endpoint high_saha on network bridge:
failed to add the host (veth7f6f907) <=> sandbox (veth788d9dc) pair interfaces: operation not supported

(I have just upgraded my Debian server from Wheezy to Jessie)

Does anyone has an idea why I get this error? Did I missed something during the upgrade?

Thanks for your help.

Solution 1

You've booted your system with OVH's custom kernel, which is built to OVH's specifications, and may not be suitable for running software you want to run.

Change your dedicated server configuration to boot from the kernel installed on the hard drive provided by your Linux distribution.

Solution 2

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

Solution 3

I had this same problem (pair interfaces: operation not supported) and I use a custom kernel. For me the cause was a missing module "Virtual ethernet pair device" CONFIG_VETH.

│ CONFIG_VETH:
│ │ This device is a local ethernet tunnel. Devices are created in pairs. When one end receives the packet it appears on its pair and vice versa. │ Symbol: VETH [=m]
│ │ Type : tristate
│ │ Prompt: Virtual ethernet pair device
│ │ Location:
│ │ -> Device Drivers
│ │ -> Network device support (NETDEVICES [=y])
│ │ -> Network core driver support (NET_CORE [=y])

hope it helps

Comments

[Michael Hampton]

What kernel are you running?

[piero-la-lune]

3.10.23-xxxx-std-ipv6-64

[piero-la-lune]

I installed a new kernel and told Grub to use it. It now works ! Thanks !

[cbley]

That is normal, since on a kernel upgrade, all .ko module files in /usr/lib/modules/{KERNEL_VERSION} of the running kernel are deleted. Docker needs some tun / tap modules to create the interfaces and trying to load them fails after a kernel upgrade. Rebooting helps because all module files are there for the new kernel. Another work-around would be to re-extract the modules for the old kernel if you still have the pacman package lying around and want to avoid the reboot.

[Daniel Andrei Mincă]

Did you reboot after kernel update?

[Nicolas Modrzyk]

same here. that made the error disappeared and the container to start properly after reboot.

[Fernando Kosh]

Also works on Manjaro. Just reboot.

[Chris Frank]

Thanks for this! Good ol' Arch...

[Ferares]

btw me too, and thank you for the tip

[Eric]

This solved the issue in the context of building my own kernel. Refer to this for other config options: blog.hypriot.com/post/verify-kernel-container-compatibility