You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Docker plugin builds to use arch-specific tags
Docker plugins don't support multi-arch manifest lists, so use
arch-specific tags instead (e.g., :latest-amd64, :latest-arm64).
- :main-* updated on every push to main
- :latest-* only updated on version tags
- :pr-N-* for internal PR testing
See specs/08_docker-plugin-architecture.md for details.
The plugin is built for multiple CPU architectures (amd64, arm64) and published to GHCR. Due to Docker plugin registry limitations, each architecture is published as a separate tag rather than a unified multi-arch manifest.
9
+
10
+
## Goals
11
+
12
+
- Support both amd64 and arm64 architectures
13
+
- Publish to GHCR on every push to main and on version tags
14
+
- Enable PR testing with dedicated tags
15
+
- Clear installation instructions for each architecture
16
+
17
+
## Non-Goals
18
+
19
+
- Unified multi-arch manifest (not supported by Docker plugins)
20
+
- Support for additional architectures (386, ppc64le, etc.)
21
+
- Automatic architecture detection during install
22
+
23
+
## Background: Docker Plugin Registry Format
24
+
25
+
Docker plugins use a different registry format than standard OCI container images:
0 commit comments