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
Create service with ports failed #939
Comments
me too |
@aluzzardi the error clearly indicates that the daemon is not running in the newly introduced |
@mavenugo So there's no way right now to use bare swarmkit with multi-host? |
Same problem with ports, but different error and configuration: Swarmd version: Docker version:
with Consul configured for KV storage for overlay networks. Commands executed:
service inspect:
Networks listing in Docker:
swarmd output:
docker logs:
Same error if I run swarmd/swarmctl as root. Without specifying any port, the container is created and connected to the "overlaynet-test" network (tried with swarmkit and manually with "docker run"). |
@Matsca09 I met the same problem. Even the docker daemon started in agent mode, the swarmkit service still can not run successfully if it's given a --port option. It looks swarmkit will try to create the default "ingress" network even user specified a different network by --network option. Unfortunately the docker daemon doesn't allow creating network named "ingress". So the swarmkit would fail at creating containers. Following code snippet indicates the reason underneath. docker/daemon/network.go:createNetwork()
docker/runconfig/hostconfig_unix.go
From swarmkit side, the default network name is defined in swarmkit/manager/allocator/network.go @aluzzardi, should we change the default network name "ingress" to avoid the problem? |
@jimmyxian I'm going through old issues here. Is this one still valid or can we close it? |
I try to create service with ports, but failed.
Cmd:
swarmkit log:
Docker daemon log:
Environment: One node
The text was updated successfully, but these errors were encountered: