Revision history [back]

I haven't yet had the chance to do a lot docker swarm with ROS since the Software Defined Network overhaul in docker/libkv a while ago, been a bit busy. But from what I remember is that you could attach two containers running from separate host (if the docker engines on those host are part of the same swarm) to a new SDNetwork you define. This is network attaching is done in the deployment example in the docs on the DockerHub ROS repo, but for only for one engine. https://hub.docker.com/_/ros/

If you want to achieve the same effect but with containers running on separate engines, you need to express this to the docker swarm master that is launching the containers on the swarm cluster. https://docs.docker.com/swarm/networking/

I haven't yet had the chance to do a lot docker swarm with ROS since the Software Defined Network overhaul in docker/libkv a while ago, been a bit busy. But from what I remember is that you could attach two containers running from separate host (if the docker engines on those host are part of the same swarm) to a new SDNetwork you define. This is network attaching is done in the deployment example in the docs on the DockerHub ROS repo, but for only for one engine.
https://hub.docker.com/_/ros/

If you want to achieve the same effect but with containers running on separate engines, you need to express this to the docker swarm master that is launching the containers on the swarm cluster. https://docs.docker.com/swarm/networking/

I haven't yet had the chance to do a lot with docker swarm with and ROS since the Software Defined Network overhaul in docker/libkv a while ago, been a bit busy. But from what I remember is that you could attach two containers running from separate host (if the docker engines on those host are part of the same swarm) to a new SDNetwork you define. This is network attaching is done in the deployment example in the docs on the DockerHub ROS repo, but for only for one engine.
https://hub.docker.com/_/ros/

If you want to achieve the same effect but with containers running on separate engines, you need to express this to the docker swarm master that is launching the containers on the swarm cluster. https://docs.docker.com/swarm/networking/

I haven't yet had the chance to do a lot with docker swarm and ROS since the Software Defined Network overhaul in docker/libkv a while ago, been a bit busy. But from what I remember is that you could attach two containers running from separate host (if the docker engines on those host are part of the same swarm) to a new SDNetwork you define. This is network attaching is done in the deployment example in the docs on the DockerHub ROS repo, but for only for one engine.
https://hub.docker.com/_/ros/

If you want to achieve the same effect but with containers running on separate engines, you need to express this to the docker swarm master that is launching the containers on the swarm cluster. https://docs.docker.com/swarm/networking/ https://docs.docker.com/engine/reference/commandline/network_connect/