error creating vxlan interface: operation not supported.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
I am able to successfully create an overlay network across multiple hosts.
However when u try to start any contains in that network i get the following error
Error response from daemon: 500 Internal Server Error: subnet sandbox join failed for "10.0.0.0/24": error creating vxlan interface: operation not supported.
Any help would be much appreciated.
Some more info about environment below
docker info Containers: 5 Running: 3 Paused: 0 Stopped: 2 Images: 4 Server Version: 1.10.3 Storage Driver: overlay Backing Filesystem: extfs Execution Driver: native-0.2 Logging Driver: json-file Plugins: Volume: local Network: overlay bridge null host Kernel Version: 4.4.9-v7+ Operating System: Raspbian GNU/Linux 8 (jessie) OSType: linux Architecture: armv7l CPUs: 4 Total Memory: 925.5 MiB Name: JasPi1 ID: BDPC:SYMO:F4GB:VJ7Z:4U3Y:H7YE:DJBA:HGMW:LWBA:SKNF:M4ZB:MKOO Debug mode (server): true File Descriptors: 41 Goroutines: 73 System Time: 2016-05-10T22:30:51.508003106Z EventsListeners: 1 Init SHA1: 0db326fc09273474242804e87e11e1d9930fb95b Init Path: /usr/lib/docker/dockerinit Docker Root Dir: /var/lib/docker WARNING: No swap limit support WARNING: No cpu cfs quota support WARNING: No cpu cfs period support WARNING: No cpuset support Labels: processor=arm Cluster store: consul://192.168.0.10:8500 Cluster advertise: 192.168.0.10:2375
Linux JasPi1 4.4.9-v7+ #884 SMP Fri May 6 17:28:59 BST 2016 armv7l GNU/Linux
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the reported Docker overlay-network startup path as the entry point, reproducing with Docker 1.10.3 on the listed ARM/Raspbian 4.4.9-v7+ environment. Compare the VXLAN failure against kernel support and determine whether a code change or an environment limitation is responsible; done means a confirmed cause and documented resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100