adamant-kite-43734
05/29/2023, 7:54 PMhigh-morning-12231
05/29/2023, 8:25 PMhigh-morning-12231
05/29/2023, 8:26 PMshy-pharmacist-48081
05/29/2023, 8:47 PMk3d cluster create test
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-test'
INFO[0000] Created image volume k3d-test-images
INFO[0000] Starting new tools node...
INFO[0000] Pulling image '<http://ghcr.io/k3d-io/k3d-tools:5.5.1|ghcr.io/k3d-io/k3d-tools:5.5.1>'
INFO[0001] Creating node 'k3d-test-server-0'
INFO[0002] Starting Node 'k3d-test-tools'
INFO[0002] Pulling image '<http://docker.io/rancher/k3s:v1.26.4-k3s1|docker.io/rancher/k3s:v1.26.4-k3s1>'
INFO[0008] Creating LoadBalancer 'k3d-test-serverlb'
INFO[0009] Pulling image '<http://ghcr.io/k3d-io/k3d-proxy:5.5.1|ghcr.io/k3d-io/k3d-proxy:5.5.1>'
INFO[0011] Using the k3d-tools node to gather environment information
INFO[0011] Starting new tools node...
INFO[0011] Starting Node 'k3d-test-tools'
INFO[0012] Starting cluster 'test'
INFO[0012] Starting servers...
INFO[0012] Starting Node 'k3d-test-server-0'
INFO[0016] All agents already running.
INFO[0016] Starting helpers...
INFO[0016] Starting Node 'k3d-test-serverlb'
INFO[0022] Injecting records for hostAliases (incl. host.k3d.internal) and for 3 network members into CoreDNS configmap...
INFO[0025] Cluster 'test' created successfully!
INFO[0025] You can now use it like this:
kubectl cluster-info
shy-pharmacist-48081
05/29/2023, 8:48 PMk3d cluster create --help
that would disable iptables or anything network related besides choosing a subnet cidr, is there ?shy-pharmacist-48081
05/29/2023, 9:38 PMk3d-init:
image: rancher/k3d
command: ["run", "-d", "--privileged", "--name", "k3d", "--hostname", "k3d", "-p", "6443:6443", "rancher/k3d"]
platform: linux/amd64
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /cache:/cache
networks:
- cloudbuild
shy-pharmacist-48081
05/29/2023, 11:17 PMshy-pharmacist-48081
05/29/2023, 11:18 PMshy-pharmacist-48081
05/30/2023, 1:36 AMStep #3: k3d | ERRO[0006] Failed to run tools container for cluster 'k3s-default'
Step #3: k3d | ERRO[0006] failed to gather environment information used for cluster creation: failed to run k3d-tools node for cluster 'k3s-default': failed to create node 'k3d-k3s-default-tools': runtime failed to create node 'k3d-k3s-default-tools': failed to create container for node 'k3d-k3s-default-tools': docker failed to pull image '<http://ghcr.io/k3d-io/k3d-tools:1afe3603|ghcr.io/k3d-io/k3d-tools:1afe3603>': docker failed to pull the image '<http://ghcr.io/k3d-io/k3d-tools:1afe3603|ghcr.io/k3d-io/k3d-tools:1afe3603>': Error response from daemon: manifest unknown
Step #3: k3d | ERRO[0006] Failed to create cluster >>> Rolling Back
shy-pharmacist-48081
05/30/2023, 1:42 AMdocker pull <http://ghcr.io/k3d-io/k3d-tools:1afe3603|ghcr.io/k3d-io/k3d-tools:1afe3603>
Error response from daemon: manifest unknown
how can i tell k3d to use a different tools image? 🤔wide-garage-9465
05/30/2023, 5:13 AMwide-garage-9465
05/30/2023, 5:15 AMshy-pharmacist-48081
05/30/2023, 4:04 PM<http://ghcr.io/k3d-io/k3d-tools:1afe3603|ghcr.io/k3d-io/k3d-tools:1afe3603>
is not a valid image, but
<http://ghcr.io/k3d-io/k3d-tools:sha-1afe3603|ghcr.io/k3d-io/k3d-tools:sha-1afe3603>
is validshy-pharmacist-48081
05/30/2023, 4:59 PMk3d-init:
image: <http://gcr.io/my-fork/k3d:latest|gcr.io/my-fork/k3d:latest>
command: ["--verbose", "cluster", "create", "--no-lb", "--image", "rancher/k3s:latest"]
depends_on:
- k3d-version
environment:
- K3D_IMAGE_TOOLS=<http://ghcr.io/k3d-io/k3d-tools:latest|ghcr.io/k3d-io/k3d-tools:latest>
platform: linux/amd64
privileged: true
container_name: k3d
hostname: k3d
ports:
- "6443:6443"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /cache:/cache
- /tmp:/tmp
networks:
- cloudbuild