-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gazebo fail after running start.sh #4
Comments
@lmark1 can you take a look? |
Hey @allenthreee, You can try now. I updated Dockerfiles and build script. |
Thank you for your swift reply. The docker image works now. |
Hey @allenthreee, It seems that the starutup folder is using an older parameter set for ardupilot. I will get it sorted by the end of today. |
Hi, @lmark1 , |
Please run the following command to update the base images: docker pull lmark1/uav_ros_simulation:focal-bin-0.0.1 or if you're not using GPU docker pull lmark1/uav_ros_simulation:focal-nogpu-bin-0.0.1 Then, run |
Hi @lmark1 , Thank you for your help, it works perfectly now. Merry Christmas! |
Good to hear! |
The error message is as follows:
/root/sim_ws/src/uav_ros_simulation/ros_packages/ardupilot_gazebo/scripts/run_copter.sh: "cat ${PARAM_PATH} >> ${IDENTITY_PATH}" command failed with exit code 1$0 $ @ /root/sim_ws/src/uav_ros_simulation/ros_packages/ardupilot_gazebo/scripts/run_copter.sh kopterworx 1 /root/uav_ws/install/share/icuas24_competition/parameters/arducopter_nogps.params false false 50 gazebo-iris ArduCopter false --no-rebuild __name:=sim_vehicle_startup __log:=/root/.ros/log/2ca6768a-9f10-11ee-b33f-a4c3f0785be 5/sim_vehicle_startup-1.log].
[sim_vehicle_startup-1] process has died [pid 26799, exit code 1, cmd bash -c sleep 1.0;
log file: /root/.ros/log/2ca6768a-9f10-11ee-b33f-a4c3f0785be5/sim_vehicle_startup-1*.log
all processes on machine have died, roslaunch will exit
There are only these 2 tags in your dockerhub, are the previous ones deleted? And I guess the bugs are related to this docker image version :)
The text was updated successfully, but these errors were encountered: