sandbox-lifecycle

You can safely run untrusted code by isolating it in an ephemeral Docker sandbox, which prevents the repository from accessing your host filesystem or privileges during execution and teardown.

Inspecting an unknown repo is best done using an ephemeral sandbox that enforces non-root read-only containers, offline-by-default networking, and no bind mounts or docker socket access to protect the host.

You can copy files out of a Docker container using a controlled file copy-out workflow that operates within the isolated sandbox lifecycle, ensuring no risky host bind mounts are re-established during extraction.

The sandbox lifecycle workflow uses offline-by-default networking, meaning external network access is restricted by default to prevent untrusted code from reaching external endpoints or your host system.

You should avoid bind mounts and docker socket access because they allow sandboxed code to reach the host filesystem and privileges, bypassing the isolation required to safely evaluate untrusted repositories.

You can clean up Docker containers after evaluation using a teardown workflow that applies label-based cleanup to remove ephemeral sandboxes and their cloned named-volumes securely.