It was my understanding that using docker stack deploy would create a service in any arbitrary worker node. And if this is true, then how can I alias directly to truck1 Ignition installation, which is supposed to be located in “truck1 machine”.
Our Ignition edge “worker” nodes are similar but not equal. Demanding Ignition Designer access by service personell from time to time. So they must be located at the correct machine.
The (initial) reason we use swarm networking here. Is to utilize docker as well as overlay network. Which fits with the rest of our IOT topologi/scheme in other projects.
I guess an very efficient way of updating all swarm nodes would be to do Ignition changes centrally towards a simulator, then pushing this to a git repo. Then to automattically pull them to the correct worker nodes. But this level of programming/scripting might be difficult to maintain for me and our company at the moment.
Docker swarm is a new “platform” for us, and we are happy for any inputs you might have!