Snaps

snapcraft

• ROS architectures with snaps
  • Monolithic architecture
    • Complexity
    • Stability
    • Size
    • Deployment
    • Reusability
  • Multi snaps architecture
    • Complexity
    • Stability
    • Size
    • Deployment
    • Reusability
  • Multi snaps using content sharing
    • Complexity
    • Stability
    • Size
    • Deployment
    • Reusability
  • Conclusion
• Identify functionalities and applications of a robotics snap
  • Robot functionalities
  • Snap applications
    • What are snap applications?
    • Define the role and the scope of the applications
• Snap configurations and hooks
  • What are hooks?
  • Snap configurations
• Snap data and file storage
  • SNAP_USER_DATA
  • SNAP_USER_COMMON
• Snap environment variables
  • SNAP
  • SNAP_INSTANCE_NAME
• Application orchestration
  • Command-chain
  • Stop-command
  • Post-stop-command
• Vcstool and rosinstall file
  • Overrides part steps
  • Using Vcstool
• Debug the build of a snap
  • Snapcraft environment
    • Project
    • Parts
    • Stage
    • Prime
    • Snap
  • Snapcraft debug
  • Snapcraft shell-after
  • Snapcraft try
• Debug a snap application
  • Snap logs
  • Snap environment
    • Snap file structure
    • Snap run
  • Snap connections
  • Snappy-debug

Snaps are containers that bundle an application and all its dependencies. As such, snaps offer a solution to build and distribute containerised robotics applications or any software.

Snaps are ideal for robotics developers,developers as they bundle all your dependencies and assets in one package, making applications installable on dozens of Linux distributions and across distro versions. You won’t even have to install anything else on your robots’ operating system, no dependencies, not even ROS if you are using it.

The creation of snaps can be integrated into your CI pipeline, making the updates effortless. Snaps can update automatically and transactionally, making sure the device is never broken.

Snapcraft, the tooling for building snaps, comes with native integrations through plugins and extensions dedicated to both ROS and ROS 2; developed and maintained by Canonical.

Note

Learn more about Snaps for robotics.