Skip to content
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

chore(docker): properly handle arm(32) and arm64 #441

Merged
merged 3 commits into from
Dec 11, 2020
Merged

Conversation

sh0rez
Copy link
Member

@sh0rez sh0rez commented Dec 11, 2020

Reverts the previous commits attempt to fix Helm on arm32 by using the Alpine package, because as it turns out, there is no alpine package for armhf.

Instead, we now use the offical Helm binaries, and go env GOOS and go env GOARCH to pick the correct one.

This should work consistently across all platforms.

Reverts the previous commits attempt to fix Helm on arm32 by using the
Alpine package, because as it turns out, there is no alpine package for
armhf.

Instead, we now use the offical Helm binaries, and `go env GOOS` and `go
env GOARCH` to pick the correct one.

This should work consistently across all platforms.
Uses the alpine version of golang consistently across the whole
Dockerfile, so no longer need to pull both, the ubuntu and the alpine
variant: use golang:alpine

Uses the alpine version of golang consistently across the whole
Dockerfile, so no longer need to pull both, the ubuntu and the alpine variant
@sh0rez
Copy link
Member Author

sh0rez commented Dec 11, 2020

I just verified manually, this one actually builds just fine on arm32, the helm, tk and kubectl binaries are indeed executable

@sh0rez sh0rez changed the title chore(docker): install Helm from binary chore(docker): properly handle arm(32) and arm64 Dec 11, 2020
@Duologic Duologic merged commit 646b8df into master Dec 11, 2020
@Duologic Duologic deleted the helm-goarch branch December 11, 2020 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants