Add Docker for testing ROS wrapper #3635
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #
About
This PR adds an example Dockerfile for testing the ROS wrapper. My current ROS install on host is broken (long story), that's why wrote this script.
docker build -t airsim-ros -f Dockerfile-ROS .
docker run --rm -it --net=host -v ~/AirSim:/home/testuser/AirSim airsim-ros:latest bash
Inside container:
source /opt/ros/melodic/setup.bash
, or add to .bashrc (echo "source /opt/ros/melodic/setup.bash" >> .bashrc
)cd AirSim/ros
,catkin build -DCMAKE_C_COMPILER=gcc-8 -DCMAKE_CXX_COMPILER=g++-8
(Basically https://microsoft.github.io/AirSim/airsim_ros_pkgs/#build)source devel/setup.bash
roslaunch airsim_ros_pkgs airsim_node.launch output:=screen
Output:
Also demonstrates that settings.json isn't required after #3536
TODO:
How Has This Been Tested?
Used the docker container to test that no settings.json file is required if using the latest master AirSim. With a 1.4.0 release, the fallback behaviour is seen -
Screenshots (if appropriate):