Docker start.sh launch issue

[afaroo01]

I am getting these issues whenever I run the docker and do start.sh. Please let me know what is causing this issue and how to resolve. Thanks

[lmark1]

Hello @afaroo01,

At the first glance it seems you are running an old base image of the UAV simulation stack.

The commands you need to run to start the challenge in Docker are as follows:

# pull the newest uav_ros_simulation image
docker pull lmark1/uav_ros_simulation:bionic

# navigate to icuas22_competition folder and pull newest changes
git pull origin main

# build the ICUAS challenge docker image
./docker_build.sh --bionic

# you might need to remove the old container if you previously ran it
docker container rm icuas22_competition_bionic

# run the challenge container
./docker_run.sh --bionic

# once in the container navigate to the startup/challenge folder and run start.sh
cd startup/challenge
./start.sh

From what I can tell the challenge runs fine on both bionic and focal distributions.

Please refer to the README.md for more instructions and explanations about building and running the challenge simulation.

Best regards, Lovro

[afaroo01]

Hi @lmark1

Thanks for your reply. I was able to remove the previous errors by doing a fresh installation. However, now the ./start.sh only shows a ground-truth and spawn a red (uav) in the models of the gazebo as you can see. No arena, obstacles and ball are seen. Can you tell what is causing it not setting up the setup?

[afaroo01]

Hi @aivano and @fpetric, might you can resolve this second issue. It's related to not seeing the arena ball and proper competition layout in gazebo after fresh installation of the setup using docker image.

[afaroo01]

@lmark1 @fpetric @aivano

Regarding the lat comment. I checked in the gazebo terminal, is says waiting for simulation and nothing appears still. Can you please help out on this issue?

[afaroo01]

The issue was resolved by running the following command in the icuas22_compeititon folder and building again.

git pull origin main

[fpetric]

Sorry for not replying sooner, busy day :) glad you got it sorted out!