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.

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

The Docker Engine you're using is running in swarm mode. Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node. #5146

Closed
nikoo56 opened this issue Aug 30, 2017 · 3 comments

Comments

@nikoo56
Copy link

nikoo56 commented Aug 30, 2017

My application was working fine but suddenly I start to get this message:

The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

I am not using swarm in my application but I worked with it before this app.

@nikoo56 nikoo56 changed the title he Docker Engine you're using is running in swarm mode. Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node. The Docker Engine you're using is running in swarm mode. Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node. Aug 30, 2017
@shin-
Copy link

shin- commented Aug 30, 2017

It's just a warning that will show up if you ran docker swarm init or docker swarm join. If you don't intend to use Swarm mode on this instance of the Docker engine, you may run docker swarm leave --force to get rid of the warning. Either way, this will not affect your application.

@nikoo56
Copy link
Author

nikoo56 commented Aug 30, 2017

I am not even running swarm commands. I only Run the project inside Visual Studio 2017 that previously was running, but now I am getting this error.

@shin-
Copy link

shin- commented Aug 30, 2017

Okay. It's not an error, it's a warning. You can safely ignore it. 👍

@shin- shin- closed this as completed Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants