Skip to content
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.

Sign up for GitHub

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

Jump to bottom

container ingress-sbox is already present in sandbox ingress_sbox #36876

Closed
Mobe91 opened this issue Apr 17, 2018 · 3 comments
Closed

container ingress-sbox is already present in sandbox ingress_sbox #36876

Mobe91 opened this issue Apr 17, 2018 · 3 comments
Labels
area/networking area/swarm status/needs-attention Calls for a collective discussion during a review session

Comments

@Mobe91
Copy link

Mobe91 commented Apr 17, 2018

When I create a fresh swarm via docker swarm init and try to deploy a service, the service is not replicated. docker service ps <service-name> shows container ingress-sbox is already present in sandbox ingress_sbox as the reason.
I have already tried to recreate the swarm but no luck.
OS version:

Debian GNU/Linux 9.3 (stretch) Kernel 4.15.11

docker version:

Client:
 Version:       18.03.0-ce
 API version:   1.37
 Go version:    go1.9.4
 Git commit:    0520e24
 Built: Wed Mar 21 23:10:06 2018
 OS/Arch:       linux/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      18.03.0-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   0520e24
  Built:        Wed Mar 21 23:08:35 2018
  OS/Arch:      linux/amd64
  Experimental: false

docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 18.03.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: ibhtk8e9ephds1hgpgamvmge1
 Is Manager: true
 ClusterID: noa781qf55qsv5t085jcpop4a
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: 134.255.247.240
 Manager Addresses:
  134.255.247.240:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.15.11-xen
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.67GiB
Name: vmanager4986.premium-vserver.net
ID: BL5V:P4HI:ZYIH:T5ZM:XG2U:EZIJ:LNPG:ZER3:EBIC:3M7H:3JBE:EZQJ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

docker network ls:

NETWORK ID          NAME                DRIVER              SCOPE
47c6d705334c        bridge              bridge              local
482bda27a9f9        host                host                local
wz2icrxxc5bo        ingress             overlay             swarm
zl9gq07zwjel        nginx               overlay             swarm
93ae6489f6e8        none                null                local

docker network inspect ignress:

[
    {
        "Name": "ingress",
        "Id": "wz2icrxxc5bosh6tgyim8egqh",
        "Created": "2018-04-17T10:05:31.817176867Z",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "",
            "Options": null,
            "Config": [
                {
                    "Subnet": "10.255.0.0/16",
                    "Gateway": "10.255.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": true,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": null,
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "4096"
        },
        "Labels": null
    }
]
@Mobe91
Copy link
Author

Mobe91 commented Apr 19, 2018 •
edited
Loading

When I create the swarm, the following message is logged in /var/log/syslog:

Apr 19 11:09:38 vmanager4986 dockerd[18779]: time="2018-04-19T11:09:38.503714386+02:00" level=error msg="Failed creating ingress network: container ingress-sbox is already present in sandbox ingress_sbox"
Apr 19 11:18:12 vmanager4986 dockerd[27993]: time="2018-04-19T11:18:12.565123184+02:00" level=error msg="Failed creating ingress network: subnet sandbox join failed for \"10.255.0.0/16\": error creating vxlan interface: operation not supported"

So it is weird that the ingress network actually shows up when running docker network ls

@anusha-ragunathan anusha-ragunathan mentioned this issue Apr 19, 2018
Open
@thaJeztah thaJeztah added the status/needs-attention Calls for a collective discussion during a review session label Apr 19, 2018
@Mobe91
Copy link
Author

Mobe91 commented Apr 20, 2018

Ok so it turns out that I was running on a XEN-virtualized server and this somehow prohibits the use of vxlan. I switched to a HVM-virtualized server and everything worked fine. Closing this.

@Mobe91 Mobe91 closed this as completed Apr 20, 2018
@OKNoah
Copy link

OKNoah commented May 4, 2018

I had a similar problem but was on KVM. The issue was the custom kernel used by Linode. Switching to GRUB 2 and rebooting resolved it. This is documented elsewhere in these Github issues pages, but thought I'd mention it here as it was one of my first search results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/networking area/swarm status/needs-attention Calls for a collective discussion during a review session
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@thaJeztah @Mobe91 @OKNoah @GordonTheTurtle