Docker Engine Debian 13 rootful¶

Native Debian 13 docker.io package with rootful Docker daemon for isolated compatibility tests

Image: ghcr.io/strukturpiloten/docker-debian-13-rootful
Declared image version: v1.0.0
Family: Docker Engine
Architecture: amd64, arm64
Inner mode: rootful

Declared runtime base: docker.io/library/debian:13@sha256:9cc080028c43b27d2074d63a5f9caf7166d731494965616c1a6d2827a004585c

Image source and metadata · GHCR package · Detailed guide

Choose and inspect¶

The distribution selects the installed engine package at build time. Inspect the published image's component manifest or SBOM for its exact revision.

Declared tags: v1.0.0, v1.0, v1, main, latest. These are publication policy aliases, not proof that any tag exists in GHCR. Even the exact SemVer tag can move after a reviewed rebuild.

Registry status: observed; checked at 2026-09-28T10:16:09.127321+00:00.

Observed latest index digest: sha256:3c2f1f77e8e2ae1cb71fcf3fb660f6ba67bcbf04cd4cd4b99fcd6a371421c9db.

Pull the observed immutable artifact:

podman pull ghcr.io/strukturpiloten/docker-debian-13-rootful@sha256:3c2f1f77e8e2ae1cb71fcf3fb660f6ba67bcbf04cd4cd4b99fcd6a371421c9db

For an isolated Linux nested-Docker test, the outer Podman boundary runs rootfully and privileged. Use a trusted runner and keep its image store separate from other tests:

sudo podman run --rm --detach --name nested-docker --privileged --device /dev/fuse --security-opt label=disable ghcr.io/strukturpiloten/docker-debian-13-rootful@sha256:3c2f1f77e8e2ae1cb71fcf3fb660f6ba67bcbf04cd4cd4b99fcd6a371421c9db
ready=0
for attempt in $(seq 1 30); do
  if sudo podman exec nested-docker docker info >/dev/null 2>&1; then ready=1; break; fi
  sleep 2
done
if [ "$ready" -eq 1 ]; then sudo podman exec nested-docker docker info; else sudo podman logs nested-docker; fi
sudo podman stop nested-docker
test "$ready" -eq 1

This fixture does not use the host Docker socket. Read the detailed guide for nested workloads.

Support and runtime contract¶

Lifecycle: maintained; admission: isolated-test; review after: 2026-10-27.

Vendor package revisions can advance with repository updates; image shares runner kernel and host security policy.

Declared runtime profiles: docker. Declared test settings are in the metadata source. Admission is policy, not evidence of a passed test.

Declared runtime test contract:

{
  "docker": {
    "mode": "rootful",
    "nestedRuntime": true,
    "outerPrivilege": "privileged"
  }
}

Registry aliases and history¶

Aliases resolved to the observed current digest: latest, main, v1, v1.0, v1.0.0.

Listed without digest resolution: run-36346260768-1-sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha256-02acc0fe9dd73c25cd0c45be161ab9144fcab334985646a597244213a7ebc963, sha256-3c2f1f77e8e2ae1cb71fcf3fb660f6ba67bcbf04cd4cd4b99fcd6a371421c9db, sha256-d218d3951f6571293dd34de09eca77c20c1e2c5b4f4c6305ce65c847af2ea8c4.

Evidence and timestamps¶

Matching release asset verified the build record and per-architecture runtime and scan evidence. Signature and provenance remain unverified in this snapshot.

Maintenance release · Evidence asset

GitHub package activity can include signatures and attestations; it does not identify when the current runnable image was published. A registry observation is a point-in-time check; mutable tags may move afterward. Use the immutable digest and maintenance evidence for an audit.