Docker Engine openSUSE Tumbleweed rootful¶

Native openSUSE Tumbleweed docker package with rootful Docker daemon for isolated compatibility tests

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

Declared runtime base: registry.opensuse.org/opensuse/tumbleweed:latest@sha256:cbbd4a30f7b776f1b0f5b33a9c9fd6d4d74af3fbd0c5a2e0d8a31ce119c9f364

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:23.787607+00:00.

Observed latest index digest: sha256:b09f747e8209da64913f533a748af926c4158adf0e0abf97b9713dcfcb0829ab.

Pull the observed immutable artifact:

podman pull ghcr.io/strukturpiloten/docker-opensuse-tumbleweed-rootful@sha256:b09f747e8209da64913f533a748af926c4158adf0e0abf97b9713dcfcb0829ab

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-opensuse-tumbleweed-rootful@sha256:b09f747e8209da64913f533a748af926c4158adf0e0abf97b9713dcfcb0829ab
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-0d8c23ed43be44c3c6c2992c8bfd07a1480abe7874102b1d01b20fb28afe2f3a, sha256-34a71e5f2cda526bd3422180b0edcd591bb2fe898ea438ebed8eb4c004c2914c, sha256-b09f747e8209da64913f533a748af926c4158adf0e0abf97b9713dcfcb0829ab.

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.