#Running k3s in `dagger`

1 messages · Page 1 of 1 (latest)

hot root
#

moving conversation here

#

all dependencies in Github Actions Runner ~60 GB as uncompressed image. So we're using a docker image only selected dependencies installed. I'm checking with kubectl at the moment.

pulsar hazel
#

Wouldn’t stargz support solve the image size problem if we made sure the gale base image is stargz-enabled?

hot root
#

I found the issue, it wasn't a dependency issue, it's a networkign issue I just missed

#

[command]/usr/bin/docker run -d --privileged --name=k3s-v1.27.2-k3s1 --expose=6443 -e K3S_KUBECONFIG_OUTPUT=/tmp/output/kubeconfig-v1.27.2-k3s1.yaml -e K3S_KUBECONFIG_MODE=666 -v /tmp/output:/tmp/output -p 6443:6443 -p 80:80 -p 443:443 -p 8080:8080 rancher/k3s:v1.27.2-k3s1 server

E1114 01:37:36.646096 30521 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": dial tcp 127.0.0.1:6443: connect: connection refused

it's trying to connect k3s cluster from the local port but docker instance is running behind a service.

#

probably it's related how I configure docker-in-dagger