Docker Engine 20.10 rootful¶

Upstream Docker Engine 20.10.24 static payload on maintained Alpine, rootful daemon

Image: ghcr.io/strukturpiloten/docker-20.10-rootful
Declared image version: v20.10.24
Family: Docker Engine
Architecture: amd64, arm64
Inner mode: rootful

Declared runtime base: docker.io/library/alpine:3.24@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6

Image source and metadata · GHCR package · Detailed guide

Choose and inspect¶

Declared upstream software: 20.10.24

Declared tags: v20.10.24, v20.10, v20, 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:15:26.374118+00:00.

Observed latest index digest: sha256:43b39d845f63e2edeee70806b0b323c96c87f916777586999eedffdae75ea1ba.

Pull the observed immutable artifact:

podman pull ghcr.io/strukturpiloten/docker-20.10-rootful@sha256:43b39d845f63e2edeee70806b0b323c96c87f916777586999eedffdae75ea1ba

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-20.10-rootful@sha256:43b39d845f63e2edeee70806b0b323c96c87f916777586999eedffdae75ea1ba
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: legacy; admission: isolated-test; review after: 2026-10-27.

Pinned static Engine and bundled dependencies are not patched by Alpine OS rebuilds; isolated compatibility fixture only.

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, v20, v20.10, v20.10.24.

Listed without digest resolution: run-36338188065-1-sha-237848af5481e58c6b0fec3ee0944d644eb59867, run-36346260768-1-sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha-237848af5481e58c6b0fec3ee0944d644eb59867, sha256-25d489cd90191ee9111c6bcfadba17adc6d177358e84a95ede5b85ae9bbfb687, sha256-306e69439cac019293b51de1fac27eea49ede7d140e8d1465cf58ed0a8f2db23, sha256-43b39d845f63e2edeee70806b0b323c96c87f916777586999eedffdae75ea1ba, sha256-83ecedd8a30ba5913ee97ea698fd91b2f9b7e12331dc8153a0ce23779e405917, sha256-92a32cc510ad7b06e5646ecc58e024a427cad51a8d00f8c547109328ba98f023, sha256-9cf67b1a0d50cfa300297ef2638c16248dd5ffd1c2badc8d6dce0c46891841fd.

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.