Skip to content

Provide image for arm64 #530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
everflux opened this issue Jan 15, 2019 · 10 comments
Closed

Provide image for arm64 #530

everflux opened this issue Jan 15, 2019 · 10 comments
Labels
area/container For all bugs related to the kaniko container kind/enhancement New feature or request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@everflux
Copy link

Actual behavior
Currently only amd64 architecture is supported

Expected behavior
Multi-arch images of the kaniko executor for amd64 and arm/arm64 are provided.

@MansM
Copy link

MansM commented Feb 21, 2019

It actually builds on arm and arm64:
Arm64: https://www.trion.de/news/2019/02/01/kaniko-arm-image.html
Arm32: https://gist.github.com/MansM/d72295cc7214fc11f258ba7a22605d2e

On arm32 I have some weird issues:

  • need to specify arch in Dockerfile
  • arm32v7/fedora pulls
  • arm32v7/golang:1.10 doesn’t get pulled by Kaniko, docker itself pulls fine

@lisa
Copy link

lisa commented Apr 22, 2019

@MansM I believe #646 addresses the need to specify arch in the Dockerfile.

@donmccasland donmccasland added area/container For all bugs related to the kaniko container priority/p3 agreed that this would be good to have, but no one is available at the moment. labels Sep 24, 2019
@cvgw cvgw added the kind/enhancement New feature or request label Dec 23, 2019
@njgraham
Copy link

I would love to see an aarch64 image provided. Meanwhile, I may try out the instructions linked by @MansM (with help from Google translate) - maybe it's not too difficult.

@qbasicer
Copy link

It would be great to have this officially supported as the solution linked by @MansM no longer works out of the box.

@mickkael
Copy link
Contributor

It would be great to have this officially supported as the solution linked by @MansM no longer works out of the box.

It seems to be available now.
https://github.com/GoogleContainerTools/kaniko/releases/tag/v1.3.0

@ghost
Copy link

ghost commented Nov 10, 2020

It would be great to have this officially supported as the solution linked by @MansM no longer works out of the box.

It seems to be available now.
https://github.com/GoogleContainerTools/kaniko/releases/tag/v1.3.0

I think this issue can be closed. But still missing debug images for arm64: #1488

@gabrielfreire
Copy link

Help please!

I have a cluster deployed in a couple of Raspberry PIs and am trying to build a Tekton pipeline for my project but it became an incredibly frustrating experience as i'm getting the following error from gcr.io/kaniko-project/executor@sha256:b44b0744b450e731b5a5213058792cd8d3a6a14c119cf6b1f143704f22a7c650

could not find command for platform "linux/arm64/v8"

According to Kaniko this image supports multiple architectures including arm64

My K8s cluster is version v1.20.6 so I had to install Tekton v0.32.4

What should I do ? Is there any more specific image I could try ? I have already tried

  • gcr.io/kaniko-project/executor:1.5.1
  • gcr.io/kaniko-project/executor:1.6.0
  • gcr.io/kaniko-project/executor:1.7.1
  • gcr.io/kaniko-project/executor:1.8.1
  • gcr.io/kaniko-project/executor:latest

@imjasonh
Copy link
Contributor

arm64 images are provided, so this can be closed.

As for #530 (comment), a similar platform selection bug was fixed in Kaniko by #2025 which I believe is available in 1.8.1.

But the could not find command for platform "linux/arm64/v8" sounds like a Tekton bug, specifically tektoncd/pipeline#4548, which may be fixed in a later Tekton version than v0.32.4.

If you get a chance to try a later Tekton release, and this still happens, let me know.

@gabrielfreire
Copy link

Thanks for your response, I've updated my cluster to v1.22+ and installed latest Tekton and it worked fine, not out of the box though

  • i had to create a custom kaniko task that pulls docker.io/library/bash:latest for step step-write-url as the default one didn't work for arm64

@imjasonh
Copy link
Contributor

That sounds like a bug in the kaniko task, the bash image should support arm64, I'm not sure what tag that digest points to but it looks wrong.

Anyway I'm glad you were able to get this working with the latest Tekton! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/container For all bugs related to the kaniko container kind/enhancement New feature or request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

10 participants