Request for Classic Confinement: instant-lab


  • name: Instant lab

  • description: Instant Lab is an interactive, Docker-based cybersecurity practice lab designed for Linux and Raspberry Pi systems to provision intentionally vulnerable containers and monitoring stacks.

  • snapcraft: https://github.com/swayan-basu/Instant_lab/blob/main/snap/snapcraft.yaml

  • upstream: https://github.com/swayan-basu/Instant_lab/

  • upstream-relation: I am the author/maintainer of the upstream project.

  • supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments

  • reasoning: instant-lab requires classic confinement because strict confinement sandbox restrictions block low-level host access. Specifically, it must communicate directly with the host system’s Docker daemon socket (/var/run/docker.sock) to manage local lab containers and interact with host network namespaces and security tooling, which cannot be achieved using standard strict confinement interfaces alone.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

Please use the template outlined here:

This request has been added to the queue for review by the @reviewers team.

This seems to be a duplicate, continuing this request in this thread.