CODEWITHSUNDEEP
dockerservicedocker-swarm
niqui
niqui

Reputation: 1750

Docker swarm run tasks only in workers

Say that we are working in swarm mode and we have three nodes:

Is it possible to create a service and specify that the tasks only has to run in the workers (worker1 and worker2) and not in the managers (manager1)

I am running the following command to create the service:

docker-machine ssh manager1 "docker service create --network dognet --name dog-db redis"

and when I ps the service:

docker-machine ssh manager1 "docker service ps dog-db"

I get:

ID                         NAME      IMAGE  NODE      DESIRED STATE  CURRENT STATE            ERROR
3kvfpbhl6fj0qwtglc5k7sbkw  dog-db.1  redis  manager1  Running        Preparing 4 seconds ago

Upvotes: 12

Views: 9506

Answers (3)

Lee
Lee

Reputation: 31040

The way to do this with stack deploy is via a docker-compose.yaml or stack-deploy.yaml file is containing the deploy.placement.constraints key:

#stack-deploy.yaml
services:
    your_service:
        deploy:
            placement:
                constraints:
                    -"node.role==worker"

This constraint will be picked up by the stack deploy command:

$ docker stack deploy -c stack-deploy.yaml your_app

https://docs.docker.com/engine/reference/commandline/service_create/#constraint

Upvotes: 0

abronan
abronan

Reputation: 3439

While you can use constraints (with --constraint node.role=worker) to eliminate a subset of nodes based on their role (manager or worker), I would go as far as disabling the Manager(s) from acting like Worker(s) with:

# Disables the Manager as a Worker node

docker node update --availability drain manager1

The idea is that the Manager should be kept secure from resource overload (CPU, RAM, fds), that could happen if the resources used by deployed services is higher than the resources available on a Manager. It can trigger a failure cascade scenario and the cluster could become highly unstable (or not responding to any more requests).

The Manager, at its core, maintains critical components (like certificate issuance and rotation, distributed datastore, networking), it would be bad to make your entire cluster unstable because the Managers are running out of resources.

Related Issues:

Source: I was a maintainer of Docker Swarm and wrote the Administration Guide for Swarm mode.

Upvotes: 21

johnharris85
johnharris85

Reputation: 18916

Yes, you can constrain a service based on node role. Change your command to:

docker service create --network dognet --constraint node.role==worker --name dog-db redis

Upvotes: 7

Related Questions