moby: 1.8 - "failed sandbox add: failed to add interface vethaca7063 to sandbox: failed in prefunc: failed to get link by name \"vethaca7063\": Link not found"
Potentially related to https://github.com/docker/docker/issues/14738
I’m having difficulty reproducing the issue but I had a number of errors saying “failed sandbox add: failed to add interface vethaca7063 to sandbox: failed in prefunc: failed to get link by name "vethaca7063": Link not found” with the latest 1.8 RC2 build which is concerning.
# docker version
Client:
Version: 1.8.0-rc2
API version: 1.20
Go version: go1.4.2
Git commit: 8a9d4ea
Built: Tue Aug 4 02:46:08 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.8.0-rc2
API version: 1.20
Go version: go1.4.2
Git commit: 8a9d4ea
Built: Tue Aug 4 02:46:08 UTC 2015
OS/Arch: linux/amd64
# docker info
Containers: 1579
Images: 327
Storage Driver: aufs
Root Dir: /home/docker/data/aufs
Backing Filesystem: extfs
Dirs: 3491
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-18-generic
Operating System: Ubuntu 15.04
CPUs: 8
Total Memory: 94.41 GiB
Registry: https://index.docker.io/v1/
# uname -a
Linux ns3001358.ip-37-59-48.eu 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Reactions: 1
- Comments: 108 (57 by maintainers)
Same here, Arch Linux, rebooting fix it, It might be related to the recent system update.
Issue occurred to me as well on Arch Linux after upgrading Kernel to
4.10.9-1-ARCHI didn’t reboot and thevethmodule wasn’t loaded.✅ After rebooting, module loaded and everything was back to normal.
Experiencing the same bug, Docker on Arch. 1.10.3
Another one with this issue on ArchLinux with docker 1.11.1
@JacobHenner @Yugge @oryband did you find a workaround/fix?
EDIT: rebooting somehow worked to fix that
unfortunately this doesn’t work anymore:
does anybody know if there is an alternative to rebooting every time the kernel is updated?
i’m using Arch Linux so this happens quite frequently.
On 1.12.1 my solution was to add the kernel module veth (Virtual ethernet pair device): did that help?
It’s in Device Drivers -> Network device support -> Network core driver support.
Turned out I needed to add the option VETH (module name veth).
This can happen if the kernel is updated, but you’re still running the old kernel. You can’t modprobe the veth mod for the new kernel since it’s not running. That’s why rebooting helps.
@kathiedart suprisingly this solved my problem! i executed
modprobe veth, restarted the docker service, and it worked! thanksMaybe this should be taken to the Arch community instead?
@Keats yes, rebooting does fix that. Oddly enough restarting the
docker.servicedoesn’t do the trick. Why is this happenning?Also get the same issue on Docker 1.10.3 in Arch.
SAV was also causing me problems, but I was able to get around this problem by updating my 14.04 kernel from 3.13.0 to 3.19.0-43.