ROS FAQ & Troubleshooting
This page reference ROS and ROS 2 snap common questions and troubleshooting:
Frequently Asked Questions
If you cannot find an answer to your question here, feel free to ask it on the snapcraft forum.
- I cannot snap my application. What should I check?
- Snapcraft uses the familiar ROS tools (
rosdep
/catkin
/colcon
etc). Which means that your application must follow the ROS directives for proper packaging, such as declaring all the necessary dependencies in the package.xml files or the install rules in your CMakeFile.txt. Make sure that these are in good order before attempting to create a snap.
- Snapcraft uses the familiar ROS tools (
- Which base should I use, (
core18
,core20
orcore22)
?- You should use the base that corresponds to your ROS version. That is,
-
core18
for ROS Melodic and ROS 2 Dashing -
core20
for ROS Noetic and ROS 2 Foxy. -
core22
for ROS 2 Humble.
-
- You should use the base that corresponds to your ROS version. That is,
- For ROS 1, do I have to expose
roscore
from my snap?- Exposing a
roslaunch
command from your snap will automatically launch aroscore
if needed. The only reason to expose explicitly the roscore would be if you plan to start theroscore
explicitly from your snap.
- Exposing a
- Where should my snapcraft.yaml file live?
- Within the package:
- In
core20
the snap/ directory should be located at the root of the package (next to your package.xml file) - In
core18
the snap/ directory should be located either one folder behind your package root or at the root of your workspace
- In
- Outside the package:
- Using a
rosinstall
file to download the sources. - Using a single git repository holding the sources.
- Using a
- Within the package:
Troubleshooting
- The command(s)
rosrun
and/orroslaunch
are not available in my snap.- If this happens, it means that your ROS project does not define a runtime dependency on either
rosrun
norroslaunch
anywhere. You can fix this by declaring the dependency in the appropriate ROS package.xml file. Another option is to list either (or both) ROS packages asstage-packages
in your snapcraft.yaml. The ROS packages forrosrun
androslaunch
are respectively:ros-${ROS-DISTRO}-rosbash
-
ros-${ROS-DISTRO}-roslaunch
.
- If this happens, it means that your ROS project does not define a runtime dependency on either
- With
core18
Catkin plugin creates an external link that prevents the security checks to pass.- Please see: Catkin generating an external link.
- Missing
lapack
and/orblas
.- Paths to the libraries
lapack
andblas
are not included in the library path by default. Thus, it must be extended manually in your app.environment: "LD_LIBRARY_PATH": "$LD_LIBRARY_PATH:$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/blas:$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/lapack"
- Paths to the libraries
- Warning: “This part is missing libraries that cannot be satisfied with any available stage-packages known to snapcraft”.
- Some libraries are build-time only dependencies, but are still reported as run-time dependencies by
snapcraft
. This warning is a false positive and will be fixed soon in snapcraft. For instance, when snappingros2-demo
you might encounter:This part is missing libraries that cannot be satisfied with any available stage-packages known to snapcraft: # false-positive, none of the following are necessary at run-time libnddsc.so libnddscore.so libnddscpp.so librosidl_typesupport_connext_c.so librosidl_typesupport_connext_cpp.so librticonnextmsgcpp.so
- Some libraries are build-time only dependencies, but are still reported as run-time dependencies by
- Strictly confined ROS 2 snaps shows an access error regarding shared memory.
If you see something similar to:
ROS 2 communication library is trying to use the shared memory mechanism. Don’t worry, even if you see this error, the messages are going to be transmitted (just not through shared memory). If you want to use the shared memory of ROS 2 within snap, visit: ROS 2 shared memory in snap[RTPS_TRANSPORT_SHM Error] Failed to create segment 86bb3c83d0835208: Permission denied -> Function compute_per_allocation_extra_size [RTPS_MSG_OUT Error] Permission denied -> Function init
Last updated 5 months ago.