alpine-docker / helm Goto Github PK

Would be nice if you could ship a container for the recently released v3.0.0-beta.1

https://github.com/helm/helm/releases/tag/v3.0.0-beta.1

Many thx for your efforts,
greets,
Peter

Since 3.6.x it seems the images are ppc64le only?

$ docker run alpine/helm:3.6.1
WARNING: The requested image's platform (linux/ppc64le) does not match the detected host platform (linux/amd64) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error

$ docker run alpine/helm:3.6.0
WARNING: The requested image's platform (linux/ppc64le) does not match the detected host platform (linux/amd64) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error

Tag 3.5.4 works fine:

$ docker run alpine/helm:3.5.4    
The Kubernetes package manager

Common actions for Helm:

- helm search:    search for charts
- helm pull:      download a chart to your local directory to view
- helm install:   upload the chart to Kubernetes
- helm list:      list releases of charts

Is this intented or did it break with #38 ?

currently latest release of helm is 1.13.1 accessible by https://github.com/helm/helm/releases/latest while the next two releases are prereleases and must not be tagged by latest on docker hub. or there should be stable tag too

https://github.com/docker-library/official-images#consistency

All official images should provide a consistent interface. A beginning user should be able to docker run official-image bash (or sh) without needing to learn about --entrypoint

As the entrypoint is set to helm this does not work. On jenkins the default docker container command is cat to halt the image to allow other processes to be run inside it. Since the entrypoint is set to helm the command is essentially helm cat which is not valid.

Please consider unsetting the entrypoint or creating an entrypoint script to run commands that can be found on $PATH else run helm with the arguments specified.

Not had time to look in to this yet but v3.0.0-beta.3 is not being built. It's been out for 20+ days.

https://github.com/helm/helm/releases/tag/v3.0.0-beta.3

I implemented the multi arch in this image recently, but in fact, I don't have other arch environments to test it. I can only test under amd64

If you have different environments, I would be appreciated if you can run a test on it.

The versions 2.16.10, 2.16.11, and 2.16.12 are missing.

It would we really great to have {major} and {major}.{minor} tags in addition to {major}.{minor}.{patch} so that one can pull using somthing like:

docker pull alpine/helm:3

It looks to me like the documentation on Docker Hub is out of date with regards to volumes. It doesn't match what is in the current readme. Would it be possible to update this? I spent nearly an hour sorting out that I needed to mount /root/.cache/helm, not just /root/.helm

The dockerhub "Usage" documentation is incorrect:

https://hub.docker.com/r/alpine/helm

docker run -ti --rm -v $(pwd):/apps \
    -v ~/.kube:/root/.kube \
    -v ~/.helm:/root/.helm \
    alpine/helm

The GitHub README correctly describes Usage:

docker run -ti --rm -v $(pwd):/apps -w /apps \
    -v ~/.kube:/root/.kube \
    -v ~/.helm:/root/.helm \
    -v ~/.config/helm:/root/.config/helm \
    -v ~/.cache/helm:/root/.cache/helm \
    alpine/helm

The .config and .cache directories are missing from dockerhub losing e.g. repo persistence across invocations:

Assuming the following are prefixed:

docker run \
--interactive --tty --rm \
--volume=${HOME}/.kube:/root/.kube \
--volume=${PWD}/:/apps \
--volume=${PWD}/.helm:/root/.helm \
alpine/helm:3.5.2 ...

Then:

repo list
Error: no repositories to show

repo add xxxx ...
"xxxx" has been added to your repositories

repo list
Error: no repositories to show

Nit: for documentation, I think it's more helpful to use --long-flags to aid clarity and be more inclusive of those less familiar

Title says it all - Helm 3.6 has been out for a couple of weeks now

Please consider adding kubectl or kustomize to the image. kustomize is the most common tool used in Helm post rendering, and mentioned several times in the docs:
https://helm.sh/docs/topics/advanced/

kustomize has since been integrated into kubectl (as kubectl kustomize, kubectl apply -k, etc.), so I think it would be preferable to include the latter as it could be a handy tool to have in other situations as well.

last update caused my ci cd pipeline to fail with an error

$ helm init --upgrade
Error: unknown flag: --upgrade

helm ls yields
Error: incompatible versions client[v2.14.0-rc.2] server[v2.14.0]

Yesterday Helm 3.10.3 was released. Usually the images are built weekly on thursdays around this time, but looking at the build logs it seems like there hasn't been any builds for 4 weeks.

Is there a change in the build schedule, or is it actually frozen?

Hi,

today with the latest build, the latest image tag pins to the digest (9d9fab00e068) of version 2.16.3.
The days before, latest tags to the version 3 image.

I think thats an error and should be corrected.

Regards,
Frank

Helm 3.12.0 contains a few problems, it would be awesome to build a version with 3.12.1 fixes

Hi Team,

I am trying with the docker helm image and getting the below error.
Can you help me on below.

Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused

Expected output: able to see the list of releases.
Let me know for any more inputs.

Question: will the automated build never create the new docker image in the 2.14.x range since v3.0.0-alpha.1 is technically a newer version?

Thank you :)

please, thanks!

Actually image alpine:edge can run apk update or apk add.

`/ # apk update

fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/edge/main: No such file or directory
WARNING: Ignoring APKINDEX.066df28d.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/edge/community: No such file or directory
WARNING: Ignoring APKINDEX.b53994b4.tar.gz: No such file or directory
2 errors; 14 distinct packages available

/ # apk add --no-cache curl

fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
curl (missing):
required by: world[curl]`

Hi Team,

I am trying to use “helm” over ARM64v8 but it seems it does not have an arm64 supported tag in docker hub. After the below changes, the image was successfully uploaded to Dockerhub.

• Dockerfile: Added a new build argument ARCH which will install the binaries as per the architecture.

• .travis.yml: Added architecture arm64-graviton2 and installed jq in .travis.yml file to build, test, and release image for arm64.

• Build.sh: Added check so that the image for arm64 will be pushed with name :-arm64 and also provided the architecture as build argument for building the image for a particular architecture.

Commit Link: https://github.com/Fayeal/helm/commit/86a79a6b989ceecdc357c7275996412d48c2481f

Travis Link: https://travis-ci.com/github/Fayeal/helm/builds/213286679

Dockerhub Link: https://hub.docker.com/repository/docker/odidev/helm

It looks that you are using travis-ci.org and as per https://blog.travis-ci.com/2020-09-11-arm-on-aws the arm64-graviton support is added for travis-ci.com and travis is also shutting down travis-ci.org.

It will be very helpful if this image is released for the arm64 platform. If interested, I can raise a PR. But first, we need to migrate this project from travis-ci.org to travis-ci.com.

Please let me know if any help is required.

Since the master tag was updated some hours ago, we're seeing segmentation faults when running helm.

Docker alpine was switched from edge to 3 following #13, but we want to keep using alpine:edge to be able to install/use python 3.8 (instead of 3.7) for some reasons (3.7 has some bugs that broke our pipeline).

Is it possible to have the alpine version as selectable tag?

Hello! I try use this image in .gitlab-ci.yml in docker exector.
My .gitlab-ci.yml:

image: alpine/helm:3.12.3

variables:
  NAMESPACE:
    value: "default"

stages:
  - lint
  - check chart

lint:
  stage: lint
  script:
    - helm lint .
    - helm template .
  tags:
    - docker

dry-run:
  stage: check chart
  script:
    - helm -n "$NAMESPACE" ls
    - >
      helm -n default upgrade -i --dry-run --debug app-chart . 
  tags:
    - docker

Can the alpine project create a helm image for run in .gitlab-ci.yml ?

Not sure why I would be getting this error. Any suggestions?

❯ helm version
Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}

❯ docker run -ti --rm -v $(pwd):/apps -v ~/.kube:/root/.kube alpine/helm:2.6.1 version
Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
Error: cannot connect to Tiller