-
Notifications
You must be signed in to change notification settings - Fork 2k
"subnet sandbox join failed for "10.0.0.0/24": error creating vxlan interface: operation not supported" #2753
Comments
What version of the kernel have you got on the host? |
4.1.5-x86_64-linode61 |
Same here, but I'm not using compose, just simply Docker and the overlay network driver. Kernel: After restarting the VM, things work. |
And same here on Linode.. it is a kernel issue. Even Linode tells you that the box runs 4.x, if you install the official kernel (>=3.16) AND set the linode up to boot from GRUB2, then it will work. |
Closing. This is a kernel issue |
Sorry guys, I have the same issue here. but I don't understand what is the reason. could somebody tell a bit more details? |
You probably have a kernel that's too old or it's not supported. |
well this how i get confused. the kernel version is not old, but i still get this error.
|
Yep, Linode's 4.4 kernel has this problem. Install a signed kernel (like lts-wily) from the Ubuntu repo, make sure that Linode actually boots that kernel (somewhere in the VM settings), then you're good to go.
Dashboard -> Edit profile -> Kernel -> Grub2 |
Thanks a lot. This really solved the problem. :) |
I don't know, unfortunately. |
Apologies if it's a silly question, but I also have this problem. What entries are needed in /etc/apt/sources.list for the apt-get install to work, as I haven't had any luck getting it to work with the things I've tried. |
never mind - found out about trusty/trusty-updates repositories |
To those who may experience this issue even with recent kernels. |
Thanks @matevarga. Same here today on Linode with CentOS 7. I didn't have to install the kernel myself though, just rebuilt the machines and set them to GRUB 2 in Linode's panel before first starting them. |
I've been struggling with Docker Swarm in Linode for about 2 days, so, here are my instructions on how to solve it for anyone else that arrives here. Here are the instructions with screenshots, because I think it's quite easy to get lost in the procedure and I hope others can avoid all the struggle.
|
Thanks for the find @tiangolo Worked perfectly |
Thanks @tiangolo worked perfectly for me |
In case anyone follows @tiangolo 's instructions on an older Linode and is left staring with at the Grub prompt fromm Lish, see: https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel/#older-distributions |
I am facing the https://www.linode.com/docs/platform/manager/how-to-change-your-linodes-kernel/#no-upstream-kernel-installed problem :-( Ubuntu Server 16.04 LTS
References: |
Just noting that 10.0.0.0/24 is an invalid subnet. The first valid subnet within the 10.0.0.0/8 (Class A) network, now sliced with a For any given subnet mask there are 2x - 2 subnets and 2x - 2 hosts ...where x is the number of bits on that side of the mask. So for This should make sense to anyone who already knows that you similarly can't bind any |
I've started getting this on 19.03 Docker Swarm |
I've run into a problem running docker-compose on a swarm which was setup using the "Get started with multi-host networking" article on docker.com , except using the Generic Driver
Everything seems fine for each of the hosts
Configuring swarm...
Checking connection to Docker...
Docker is up and running!
However when I run this command (Using only docker hub listed containers )
ERROR: Cannot start container 4f55c34c5687bc810aaafd58f22d0a60a118d353bc4209993881265e25d171a8: subnet sandbox join failed for "10.0.0.0/24": error creating vxlan interface: operation not supported
The text was updated successfully, but these errors were encountered: