Docker Engine 28 rootful¶

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

Image: ghcr.io/strukturpiloten/docker-28-rootful
Declared image version: v28.5.2
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: 28.5.2

Declared tags: v28.5.2, v28.5, v28, 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:52.373737+00:00.

Observed latest index digest: sha256:3aa9461e150cc1a1a87c43f4a92f5c7d73e00be27418b9fa5f570bf2a0969edf.

Pull the observed immutable artifact:

podman pull ghcr.io/strukturpiloten/docker-28-rootful@sha256:3aa9461e150cc1a1a87c43f4a92f5c7d73e00be27418b9fa5f570bf2a0969edf

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-28-rootful@sha256:3aa9461e150cc1a1a87c43f4a92f5c7d73e00be27418b9fa5f570bf2a0969edf
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, v28, v28.5, v28.5.2.

Listed without digest resolution: run-36346260768-1-sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha-0b136a13a8bb612d91960ae5d07e72f449c89ec1, sha256-3aa9461e150cc1a1a87c43f4a92f5c7d73e00be27418b9fa5f570bf2a0969edf, sha256-6afce4dd0221af9f0c70e03153295520fac3aca8dfd9bea39a44214bae18cb02, sha256-6e68ea65ee764817ac44fe631db205d602ad66ad8944e01bf3accd8a07eb347a.

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.