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
According to the documentation when calling build_image_layers.sh the image key passed with -i should have the platform key prepended to it however on release 3.2 this is not the observed behavior.
pwmarshall@pwmarshallUbuntu22:~/Lunabotics$ ./src/isaac_ros/isaac_ros_common/scripts/build_image_layers.sh -i ros2_humble
Target image name not specified, using ros2_humble-image
Building layered image for key ros2_humble as ros2_humble-image
I think build_image_layers not prepending platform key is the expected behavior as running run_dev.sh will prepend the platform key before calling build_image_layers.sh. This means that the documentation just need a slight update.
pwmarshall@pwmarshallUbuntu22:~/Lunabotics$ ./src/isaac_ros/isaac_ros_common/scripts/run_dev.sh -i ros2_humble
Launching Isaac ROS Dev container with image key x86_64.ros2_humble: /home/pwmarshall/Lunabotics
Building x86_64.ros2_humble base as image: isaac_ros_dev-x86_64
However run_dev.sh does not append user to the image key like stated in the documentation. This could be do to the fact that release 3.2 just refactored the docker images and removed the user image.
The text was updated successfully, but these errors were encountered:
Some of the documentation from this webpage https://nvidia-isaac-ros.github.io/repositories_and_packages/isaac_ros_common/index.html#isaac-ros-dev-scripts does not match what happens on release 3.2.
According to the documentation when calling
build_image_layers.sh
the image key passed with -i should have the platform key prepended to it however on release 3.2 this is not the observed behavior.I think build_image_layers not prepending platform key is the expected behavior as running
run_dev.sh
will prepend the platform key before callingbuild_image_layers.sh
. This means that the documentation just need a slight update.However
run_dev.sh
does not append user to the image key like stated in the documentation. This could be do to the fact that release 3.2 just refactored the docker images and removed the user image.The text was updated successfully, but these errors were encountered: