CLI for vehicle platform about adore HOT 5 CLOSED

given branch is intended for build system dev

from adore.

Just a comment to characterize the issue and a possible solution with some facts:

• In the docker-compose.yaml the ros-master service is currently described as a sperate service
• With docker compose >v3, which we are using docker swarm can be used
• Using docker swarm hostnames for each service can be defined in the docker-compose files
• A new section needs to be added to the docker-compose file called deploy:

from adore.

Sounds great. Unfortunately, the ROS master in the car is not under our control. The pc running the ROS master is not using compose >v3 and it is starting the ROS master in a different manner.

from adore.

• ing docker swarm host names for each service can be defined in the docker-compose files
• A new section needs to be add

Its simple then, we need a different docker compose file for the vehicle that excludes the rosmaster service and changes the environment variables for the ros master in the adore cli service.

With #52 I have made this process easier by splitting the adore cli services into their own distinct docker compose file adore-cli.yaml.

I have added a recommended change as a comment here: https://github.com/eclipse/adore/pull/52/files#r1037083544

from adore.

got fixed in the car-repo (sorry this is not public)

from adore.