Skip to content

Use the multi-arch gesellix/registry image#315

Merged
gesellix merged 1 commit into
mainfrom
use-multiarch-registry-image
Jun 13, 2026
Merged

Use the multi-arch gesellix/registry image#315
gesellix merged 1 commit into
mainfrom
use-multiarch-registry-image

Conversation

@gesellix

Copy link
Copy Markdown
Contributor

Now that gesellix/registry:<tag> is published as a single multi-arch manifest (linux/amd64, linux/arm64, Windows ltsc2022 + ltsc2025) by the image.yml workflow, DockerRegistry no longer needs to branch on the host OS.

Changes

  • Drop the LocalDocker.isNativeWindows() branching that picked between gesellix/registry:3.1.1-windows-ltsc2022 and registry:3.1.1.
  • Use the single gesellix/registry:3.1.1 manifest for every platform; the daemon pulls the variant matching its own OS and architecture.
  • The DOCKER_REGISTRY_IMAGE_OVERRIDE system property still overrides the default.

Notes

  • LocalDocker.isNativeWindows() is now unused (only available() is still referenced, by the test). Left in place; can be removed in a follow-up.

🤖 Generated with Claude Code

Now that gesellix/registry:<tag> is published as a single multi-arch manifest
(linux/amd64, linux/arm64, Windows ltsc2022 + ltsc2025), drop the
isNativeWindows() OS branching and use the one manifest for every platform; the
daemon pulls the variant matching its own OS and architecture. The
DOCKER_REGISTRY_IMAGE_OVERRIDE system property still overrides the default.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gesellix gesellix merged commit c81d9da into main Jun 13, 2026
7 of 8 checks passed
@gesellix gesellix deleted the use-multiarch-registry-image branch June 13, 2026 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant