Add docker app image#615
Conversation
8b90ba8 to
ab70271
Compare
|
Ah, I think perhaps a new workflow from a PR (from a fork) cannot access repo secrets (username and password) causing the login failure? The run here works, and will allow testing with: docker run -it will8clark/warnet-app:pr-31You should configure ~/.kube/config inside the container in the normal way. then you can interact with a cluster as usual. If you are trying to use a local cluster, then you will need to allow the docker container to talk to (outer) host with docker run --net=host -it will8clark/warnet-app:pr-31This will allow the container, when looking up a cluster with an address like |
|
Cool! This seems to work. I needed to add I was able to connect to a remote cluster by using a config file. I was also able to connect to my local minikube by copying my minikube data dir to the container. |
ab70271 to
5814b32
Compare
Thanks for testing. I added |
|
Great idea bundling all the tools into one image, saves contributors a lot of setup time. |
| COPY --from=ghcr.io/astral-sh/uv:0.4.12 /uv /bin/uv | ||
| COPY --from=ghcr.io/vladimirvivien/ktop:latest /ko-app/ktop /bin/ktop | ||
|
|
||
| RUN apk add --no-cache bash curl ca-certificates git kubectl helm k9s fish vim mc nano |
There was a problem hiding this comment.
RUN apk add --no-cache bash curl ca-certificates git kubectl helm fish vim mc nano && \ curl -sL https://github.com/derailed/k9s/releases/latest/download/k9s_Linux_amd64.tar.gz | tar -xz -C /usr/local/bin k9s
The Dockerfile build is currently broken, k9s doesn't appear to be available in the Alpine package registry, so apk add k9s fails with exit code 10. It's possible it was available when this PR was first opened but has since been removed. I Downloaded the binary directly from GitHub releases and it fixes this.
Ok I think this is better than a flatpak (more cross-platform).
Builds a docker image with:
warnetk9skubectlktop...installed.
I set
fishas the default shell, as that gets you pretty tab-autocompletion.All that's needed is to configure
~/.kube/configinside the machine (doeswarnet authdo this?), and you're good to go.Current CI is set to build PR branches and pushes to master (tagged as
latest), but we can change that if desired.I will add a test command for it after the image has built in the first run here.