Reference

Run a Chainguard Checks check once per variation, pass files between checks, check out another repository, start services such as a database or Docker, run checks as another user, and reuse Go build output with caches.

Choose the packages, tools, and network access a Chainguard Workspaces session gets, from your repository's .chainguard/develop.yaml or .chainguard/ci.yaml file, a file of your own, or the default environment.

What the Guarded Entrypoint wrapper connects to, what it never does, and what is visible in the image configuration.

Learn the network requirements for accessing Chainguard Libraries, including domains needed for authentication, package downloads, and verification tools

Differences between Chainguard Containers and Ubuntu third-party images

Reference for the chainctl checks commands that inspect pull request runs, start and rerun checks, summarize check history, and validate your Chainguard Checks configuration.

Reference for the chainctl develop commands that open and manage Chainguard Workspaces sessions, with their flags, output formats, exit codes, and the roles they need.