Name and Version
bitnami/kaniko
What is the problem this feature will solve?
The Bitnami Kaniko image (public.ecr.aws/bitnami/kaniko) only supports x86_64/amd64 architecture.
When pulled on ARM64 runners (e.g., AWS Graviton), it fails with:
"no matching manifest for linux/arm64/v8 in the manifest list entries."
What is the feature you are proposing to solve the problem?
public.ecr.aws/bitnami/kaniko should publish multi-arch manifests including linux/arm64,
similar to how other Bitnami images support multiple architectures.
Adding ARM64 multi-arch support to the Bitnami Kaniko image would provide a maintained,
version-pinnable alternative for teams building ARM64 container images in CI/CD pipelines.
What alternatives have you considered?
Using gcr.io/kaniko-project/executor:debug for ARM builds, which is a rolling tag
from an archived project with no version pinning available.
Name and Version
bitnami/kaniko
What is the problem this feature will solve?
The Bitnami Kaniko image (public.ecr.aws/bitnami/kaniko) only supports x86_64/amd64 architecture.
When pulled on ARM64 runners (e.g., AWS Graviton), it fails with:
"no matching manifest for linux/arm64/v8 in the manifest list entries."
What is the feature you are proposing to solve the problem?
public.ecr.aws/bitnami/kanikoshould publish multi-arch manifests including linux/arm64,similar to how other Bitnami images support multiple architectures.
Adding ARM64 multi-arch support to the Bitnami Kaniko image would provide a maintained,
version-pinnable alternative for teams building ARM64 container images in CI/CD pipelines.
What alternatives have you considered?
Using
gcr.io/kaniko-project/executor:debugfor ARM builds, which is a rolling tagfrom an archived project with no version pinning available.