You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The context of this error is attempting to run the husky robot from within a docker image.
The line here of the script 50.husky_find_mag_config.sh which is obviously intended to error quietly if a user provided file is not found, still provides a non-zero exit code. While this isn't a major problem, it ends up clashing with the default docker behavior in ROS' published docker images. Namely this line which forces the docker image to bail out on non-zero exit codes. Our quick workaround to simply add some commands to our docker image to copy the default file to the correct name and location in the ROS etc directory the script in question is first looking for. This fixes it and the husky robot runs nicely from the docker image, however I thought it was worth noting this minor issue.
The text was updated successfully, but these errors were encountered:
I should add, this is using the default Ubuntu Xenial / Kinetic debian packages, specifically ros-kinetic-husky-robot version 0.3.0-0xenial-20180626-092738-0800.
The context of this error is attempting to run the husky robot from within a docker image.
The line here of the script
50.husky_find_mag_config.sh
which is obviously intended to error quietly if a user provided file is not found, still provides a non-zero exit code. While this isn't a major problem, it ends up clashing with the default docker behavior in ROS' published docker images. Namely this line which forces the docker image to bail out on non-zero exit codes. Our quick workaround to simply add some commands to our docker image to copy the default file to the correct name and location in the ROSetc
directory the script in question is first looking for. This fixes it and the husky robot runs nicely from the docker image, however I thought it was worth noting this minor issue.The text was updated successfully, but these errors were encountered: