New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
lrkwz opened this Issue Oct 16, 2016 · 15 comments

Comments

Projects
None yet
10 participants
@lrkwz
Contributor

lrkwz commented Oct 16, 2016

I have a fresly installed docker but when I cannot execute containers

docker run --rm hello-world                                                                                                                          
docker: Error response from daemon: failed to create endpoint jolly_kare on network bridge: failed to add the host (veth1d85371) <=> sandbox (vethbc264f6) pair interfaces: operation not supported.

Docker info are:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.2
Storage Driver: devicemapper
 Pool Name: docker-8:1-799432-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 14.09 MB
 Data Space Total: 107.4 GB
 Data Space Available: 21.34 GB
 Metadata Space Used: 585.7 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.77 (2012-10-15)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge overlay null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.10.23-xxxx-std-ipv6-64-vps
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.854 GiB
Name: vps102867
ID: RTPT:KG2U:SH6J:5KS4:5S27:A57A:E6PV:425A:7KEF:UJKR:5WOG:FQBV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No kernel memory limit support
Insecure Registries:
 127.0.0.0/8

I've already tried to delete /var/lib/docker/network/files/local-kv.db as mentioned in similar issues with no success

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented Oct 16, 2016

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

@lrkwz

This comment has been minimized.

Contributor

lrkwz commented Oct 17, 2016

Oops ... script's output is

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: missing
- CONFIG_BRIDGE: enabled
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_NF_NAT_IPV4: enabled
- CONFIG_IP_NF_FILTER: enabled
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled
- CONFIG_NETFILTER_XT_MATCH_IPVS: missing
- CONFIG_IP_NF_NAT: missing
- CONFIG_NF_NAT: enabled
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: missing

Optional Features:
- CONFIG_USER_NS: missing
- CONFIG_SECCOMP: enabled
- CONFIG_CGROUP_PIDS: missing
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
- CONFIG_MEMCG_KMEM: missing
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_CFQ_GROUP_IOSCHED: enabled
- CONFIG_CGROUP_PERF: missing
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled
- CONFIG_NETPRIO_CGROUP: missing
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_IP_VS: missing
- CONFIG_IP_VS_NFCT: missing
- CONFIG_IP_VS_RR: missing
- CONFIG_EXT3_FS: enabled
- CONFIG_EXT3_FS_XATTR: enabled
- CONFIG_EXT3_FS_POSIX_ACL: enabled
- CONFIG_EXT3_FS_SECURITY: enabled
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: missing
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled
      - CONFIG_CRYPTO_GCM: missing
      - CONFIG_CRYPTO_SEQIV: missing
      - CONFIG_CRYPTO_GHASH: missing
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled
      - CONFIG_XFRM_ALGO: enabled
      - CONFIG_INET_ESP: enabled
      - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled
  - "ipvlan":
    - CONFIG_IPVLAN: missing
  - "macvlan":
    - CONFIG_MACVLAN: missing
    - CONFIG_DUMMY: enabled
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled
    - CONFIG_BTRFS_FS_POSIX_ACL: enabled
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled
    - CONFIG_DM_THIN_PROVISIONING: enabled
  - "overlay":
    - CONFIG_OVERLAY_FS: missing
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000

I wonder how safe can be a kernel change on a non dedicated ovh's vps

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented Oct 17, 2016

Looks like there's various things missing, perhaps best to contact ovh support?

Based on the above, I don't think this is a bug in docker, so I'll close this issue, but feel free to continue the discussion here

@thaJeztah thaJeztah closed this Oct 17, 2016

@whoan

This comment has been minimized.

whoan commented Feb 9, 2017

In my case, the error appears everytime I update my Linux kernel. It desappears 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

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented Feb 9, 2017

Arch linux is a rolling release, and is shipping with "bleeding edge" versions of packages. Because of this, it's known that Arch periodically breaks docker; for that reason we don't ship packages for Arch. It may be best to report this with Arch linux, who maintains their packages

@whoan

This comment has been minimized.

whoan commented Feb 9, 2017

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.

@VinyLimaZ

This comment has been minimized.

VinyLimaZ commented Sep 15, 2017

Thanks @whoan for your answer!

@ckyoog

This comment has been minimized.

ckyoog commented Nov 22, 2017

@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.

@stardiviner

This comment has been minimized.

stardiviner commented Jan 2, 2018

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.

@tomas

This comment has been minimized.

tomas commented Feb 1, 2018

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!

@Nowaker

This comment has been minimized.

Nowaker commented Feb 12, 2018

@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

@whoan

This comment has been minimized.

whoan commented Feb 13, 2018

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

@morancj

This comment has been minimized.

morancj commented Apr 26, 2018

@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)

@whoan

This comment has been minimized.

whoan commented Apr 27, 2018

Thanks @morancj. I fixed it on my previous comment.

@czeigler

This comment has been minimized.

czeigler commented Apr 30, 2018

Thanks whoan, that was super helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment