docs(readme): publish with a docker-container buildx builder #2

Merged
pienter merged 1 commit from docs/publish-buildx-builder into main 2026-10-24 05:00:46 +00:00
Owner

Why

Publishing 8.8.1-php8.5.12 on 2026-10-23 failed twice on steps the README did not cover. The default docker buildx driver refuses multi-platform builds ("Multi-platform build is not supported for the docker driver"), and the push of the ~185 MB ffmpeg layer failed with 499 Client Closed Request because Traefik v3 on the tools server cut request bodies after 60 s. The README's "Build and publish" section now walks through the commands that actually worked, so the next publish needs no rediscovery.

Review guide

1. Login and builder. The default buildx driver cannot push a two-platform image.

  • README.md:213-221: Forgejo login with an access token (package Read and Write scope); one-time docker-container builder di-multi.
  • Check: scope name and Settings path match Forgejo's UI.

2. Pre-push check and push. Tags are immutable, so check before overwriting.

  • README.md:223-232: docker manifest inspect for the tag, then docker buildx build --builder di-multi … --push.
  • Check: manifest inspect succeeding means the tag exists (stop); "no such manifest" means safe to push. The text says "check that the tag does not exist" without spelling out which outcome is which.

3. Upload timeout. Explains the 499 failure and where it is fixed.

  • README.md:234-237: points to readTimeout: 600s on Traefik's websecure entry point, documented in dokploy/dns/proxy.md (companion PR on pienter/dokploy).
  • Check: the cross-repo path reads clearly to someone without the dokploy repo checked out.

4. Anonymous pull check.

  • README.md:239-245: DOCKER_CONFIG="$(mktemp -d)" docker pull … skips stored credentials to prove the image is public.

Evidence

Before: following the old README, docker buildx build --platform linux/amd64,linux/arm64 … --push failed with "Multi-platform build is not supported for the docker driver"; after switching builders, the push failed with 499 Client Closed Request on the ffmpeg layer.
After: the documented commands are the ones that published 8.8.1-php8.5.12. Anonymous docker buildx imagetools inspect and docker pull worked; index digest sha256:6429894ba989d7373f795d466a2b9d946baf0743b84bd4762e9142c0a7a628ad.

  • Checks: none run (docs only).

Tests: none (docs only).

Merge Danger

Door: two-way

Blast Radius: docs-only

## Why Publishing `8.8.1-php8.5.12` on 2026-10-23 failed twice on steps the README did not cover. The default `docker` buildx driver refuses multi-platform builds ("Multi-platform build is not supported for the docker driver"), and the push of the ~185 MB ffmpeg layer failed with `499 Client Closed Request` because Traefik v3 on the tools server cut request bodies after 60 s. The README's "Build and publish" section now walks through the commands that actually worked, so the next publish needs no rediscovery. ## Review guide **1. Login and builder.** The default buildx driver cannot push a two-platform image. - [README.md:213-221](https://git.pienter.space/pienter/directus-v8/src/commit/b606995/README.md#L213-L221): Forgejo login with an access token (package Read and Write scope); one-time `docker-container` builder `di-multi`. - **Check:** scope name and Settings path match Forgejo's UI. **2. Pre-push check and push.** Tags are immutable, so check before overwriting. - [README.md:223-232](https://git.pienter.space/pienter/directus-v8/src/commit/b606995/README.md#L223-L232): `docker manifest inspect` for the tag, then `docker buildx build --builder di-multi … --push`. - **Check:** `manifest inspect` succeeding means the tag exists (stop); "no such manifest" means safe to push. The text says "check that the tag does not exist" without spelling out which outcome is which. **3. Upload timeout.** Explains the `499` failure and where it is fixed. - [README.md:234-237](https://git.pienter.space/pienter/directus-v8/src/commit/b606995/README.md#L234-L237): points to `readTimeout: 600s` on Traefik's `websecure` entry point, documented in `dokploy/dns/proxy.md` (companion PR on `pienter/dokploy`). - **Check:** the cross-repo path reads clearly to someone without the dokploy repo checked out. **4. Anonymous pull check.** - [README.md:239-245](https://git.pienter.space/pienter/directus-v8/src/commit/b606995/README.md#L239-L245): `DOCKER_CONFIG="$(mktemp -d)" docker pull …` skips stored credentials to prove the image is public. ## Evidence **Before:** following the old README, `docker buildx build --platform linux/amd64,linux/arm64 … --push` failed with "Multi-platform build is not supported for the docker driver"; after switching builders, the push failed with `499 Client Closed Request` on the ffmpeg layer. **After:** the documented commands are the ones that published `8.8.1-php8.5.12`. Anonymous `docker buildx imagetools inspect` and `docker pull` worked; index digest `sha256:6429894ba989d7373f795d466a2b9d946baf0743b84bd4762e9142c0a7a628ad`. - **Checks:** none run (docs only). **Tests:** none (docs only). ## Merge Danger **Door:** two-way **Blast Radius:** docs-only
The default docker driver cannot build linux/amd64 and linux/arm64 in
one go. Document the di-multi builder, the access-token login, the
existing-tag check, the Traefik upload timeout and the anonymous pull.
pienter deleted branch docs/publish-buildx-builder 2026-10-24 05:00:46 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pienter/directus-v8!2
No description provided.