Understand service constraints
robinplace opened this issue · 1 comments
robinplace commented
I've using a global service with label constraints to run my database containers only on specific nodes. So I created the service like this:
docker service create --name rethinkdb-master --mode global --constraint node.labels.rethink-role==master rethinkdb
The rethink-master processes on the second two nodes will never start because of their constraints.
Can we somehow detect that they're not eligible to run and have them hidden completely instead of giving the appearance that they've crashed on startup?
ManoMarks commented
No, I think you would want to show that they aren't working.