The permission, execution and release procedures use small programs and configuration files that accompany the guide. Keep them together so the commands and relative links refer to the same version. Review the files before running them, and use a trusted workstation for administrative credentials and Docker access.
Get the example files
Select Download guide on the Practitioner Guides page and extract the ZIP into a new directory. The package contains README.md, the chapters directory, and the examples directory, including the hidden .gitlab-ci.yml files. Docker images and credentials are acquired separately.
Set GSS_GUIDE_CHECKOUT to the absolute path of the extracted directory containing chapters/01-prepare.md and examples, not its parent:
export GSS_GUIDE_CHECKOUT='<absolute-path-to-extracted-guide-directory>'
Confirm the root and example files before continuing:
set -euo pipefail
cd "$GSS_GUIDE_CHECKOUT"
export GSS_GUIDE_CHECKOUT="$(pwd -P)"
test -f "$GSS_GUIDE_CHECKOUT/chapters/01-prepare.md"
test -f "$GSS_GUIDE_CHECKOUT/examples/isolated-task/task.py"
test -f "$GSS_GUIDE_CHECKOUT/examples/dedicated-runner/.gitlab-ci.yml"
test -f "$GSS_GUIDE_CHECKOUT/examples/connected-release/release_driver.py"
test -f "$GSS_GUIDE_CHECKOUT/examples/connected-response/.gitlab-ci.yml"
GSS_GUIDE_CHECKOUT always identifies these reviewed files. The private release project's Git clone is a separate directory, introduced during release setup. Keep the two paths distinct. Each procedure creates its own operating records; keep those records and any credentials out of the application repository.
Prepare the Python runtime
The isolated task and local release use Docker Desktop's desktop-linux context and a Linux ARM64 Python image. The GitLab release build runs separately on a hosted Linux AMD64 runner. These commands require Docker Desktop and jq; the release tools also need Python 3.12 or later and OpenSSL 3.
The image is referenced by digest, rather than bundled with the files. Pull it on the trusted host before starting either procedure. Pulling needs access to Docker Hub. The later task and release containers use the cached image and do not download dependencies while running. See Docker's digest-pinned pull instructions.
set -euo pipefail
export GSS_CONTEXT='desktop-linux'
export GSS_IMAGE='python@sha256:f77ac9e44ae96ef2c90b8053ea08c31f8be030f824196b0ae4db6d462c84e51f'
docker --context "$GSS_CONTEXT" context inspect "$GSS_CONTEXT"
docker --context "$GSS_CONTEXT" version
docker --context "$GSS_CONTEXT" pull --platform linux/arm64 "$GSS_IMAGE"
docker --context "$GSS_CONTEXT" image inspect "$GSS_IMAGE" | jq -e \
--arg image "$GSS_IMAGE" '
length == 1 and .[0].Os == "linux" and .[0].Architecture == "arm64" and
(.[0].RepoDigests | index($image)) != null and
(.[0].Id | test("^sha256:[0-9a-f]{64}$"))
'
Check that the context identifies the intended local daemon and that the image check returns true. The individual procedures retain their own image inspections with their operating records. A failed or interrupted download is a setup problem; inspect the local image and complete the same digest-pinned pull before proceeding. Don't substitute a floating tag or a different platform to bypass the check.
The pinned digest doesn't receive newer security fixes automatically. When changing the image, review the replacement and update its references and expected platform together before repeating the affected checks. Other architectures require a reviewed adaptation of the examples. The dedicated-runner procedure has its own acquisition and inspection steps for its Runner, matching helper, task and proxy images.