eager-hair-7480907/17/2023, 5:07 PM
eager-hair-7480907/17/2023, 6:34 PM
wide-garage-946507/17/2023, 6:37 PM
to make that work for compiled languages ( Go in this case). Otherwise there are e.g. tilt or skaffold for dev loops. In acorn (acorn.io) we have a built-in dev mode even.
delightful-magazine-134807/19/2023, 11:44 AM
, now, server is ready and agents is not ready in k3d cluster, so what should i do for resolving this problem?
Waiting to retrieve agent configuration; server is not ready: failed to retrieve configuration from server: <https://127.0.0.1:6444/v1-k3s/config>: 401 Unauthorized
handsome-salesclerk-5432407/20/2023, 12:33 PM
handsome-salesclerk-5432407/23/2023, 3:18 PM
is still required/currently works what's the current status on this issue?
thankful-insurance-405807/25/2023, 12:15 PM
still a thing? I found mentions in older articles (2021) and 1yo image in Rancher dockerhub. I am interested in controlling cluster spin up/down with docker-compose lifecycle. so
seems like a perfect option for me.
gorgeous-pizza-3656907/26/2023, 11:59 AM
wooden-coat-9775507/28/2023, 11:19 AM
thankful-insurance-405807/31/2023, 7:34 AM
image. Getting same issue as in this thread ,
Author solved it by building own dockerimage with
ip: can't find device 'ip_tables'
installed, but it seems not very maintainable for me. Github issues does not mention it. What am I doing wrong? WSL.
binary worked perfectly.
thankful-insurance-405808/01/2023, 8:28 AM
container, and configfile directory is volume-mounted to container. I'd like to achieve smth like official postgres container that runs everything in
directory after db engine start (e.g. to have some dataset populated). So I'd like
to create my cluster after start, without doing custom image based on
. • Overwriting
dos not look like the best option, (would mean having combo of calling default entrypoint plus cluster creation command), though seems easily doable. • Another idea would be some one-off container calling creation command, but
does not seem to expose some callable gimmicks out of container, and running
from other privileged container Any thoughts?
docker exec <k3d_container> /bin/k3d create --config <..>
little-dress-1357608/01/2023, 5:35 PM
handsome-salesclerk-5432408/03/2023, 8:33 PM
gorgeous-pizza-3656908/04/2023, 1:27 PM
and otherwise default networking settings. The
points to the docker network gateway, as expected (in this case
). The issue: After restarting the docker service (`systemctl restart docker`;
is enabled in docker’s
– not sure if relevant) DNS resolution no longer works (
). It starts working again after restarting the container (
nslookup: write to '192.168.30.129': Connection refused \n ;; connection timed out; no servers could be reached
docker stop/start …
k3d node stop/start …
handsome-salesclerk-5432408/05/2023, 11:13 AM
wide-oil-955008/10/2023, 12:28 PM
handsome-salesclerk-5432408/10/2023, 3:09 PM
proud-apple-2195408/13/2023, 8:48 AM
but I'm getting
k3d cluster stop k3d-mycluster
FATA No nodes found for given cluster
kubectl get nodes
I'm trying to restart my k3d cluster as I need to add a node to it
NAME STATUS ROLES AGE VERSION k3d-mycluster-server-0 Ready control-plane,master 23h v1.27.4+k3s1
proud-apple-2195408/13/2023, 6:50 PM
but upon running
k3d cluster start mycluster
, I'm getting:
kubectl get nodes
E0814 00:10:03.266044 847233 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp [::1]:8080: connect: connection refused E0814 00:10:03.266545 847233 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp [::1]:8080: connect: connection refused E0814 00:10:03.267919 847233 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp [::1]:8080: connect: connection refused E0814 00:10:03.269223 847233 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp [::1]:8080: connect: connection refused E0814 00:10:03.270505 847233 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp [::1]:8080: connect: connection refused The connection to the server localhost:8080 was refused - did you specify the right host or port?
thankful-insurance-405808/21/2023, 12:45 PM
still a thing, or it is considered to be fixed?
thankful-insurance-405808/23/2023, 11:42 AM
but there were similar questions in
github. Corporate root CA propagation to pods. I start
create cluster using config file. I have
which allows to access company's docker registry. I add helm chart to
volume and Helm controller starts installing it. Helm chart describes deployment that uses image pulled from company's registry. Ofc it gets
In regular local env usually
Head "<https://company-registry:5555/v2/my-image/manifests/my-tag>": tls: failed to verify certificate: x509: certificate signed by unknown authority
is pulled with curl (from accessible location) and appended to
. I tried to map dir containing
(whole dir as well), pass volume in k3d cluster config to server.. No success. I might be lost in this chain, what would be the correct way? Is image pulled by k3s server container env?
magnificent-midnight-1516908/23/2023, 4:29 PM
acceptable-soccer-2872008/25/2023, 7:45 AM
nameserver 22.214.171.124 options edns0 trust-ad search <http://my.domain.com|my.domain.com>
[ERROR] plugin/errors: 2 <http://my.domain.com|my.domain.com>. AAAA: read udp 10.11.12.13:35888->126.96.36.199:53: i/o timeout [ERROR] plugin/errors: 2 <http://my.domain.com|my.domain.com>. A: read udp 10.11.12.13:47750->188.8.131.52:53: i/o timeout [ERROR] plugin/errors: 2 <http://my.domain.com|my.domain.com>. A: read udp 10.11.12.13:34842->184.108.40.206:53: i/o timeout [ERROR] plugin/errors: 2 <http://my.domain.com|my.domain.com>. AAAA: read udp 10.11.12.13:45266->220.127.116.11:53: i/o timeout
ancient-florist-5915509/06/2023, 6:47 PM
ancient-florist-5915509/06/2023, 6:48 PM
rough-farmer-4913509/08/2023, 2:47 PM
works, but trying to run k3d gets
. file permissiosn are 755 and SELinux was enforcing on both installs so I don't think it's the SELinux context. I tossed a shell script with an echo command in /usr/local/bin/test.sh and set to 755 and it echoed properly. Any idea what kinda' lockdown is breaking it with normal user permission?
-bash: /usr/local/bin/k3d: Operation not permitted
handsome-salesclerk-5432409/16/2023, 12:20 PM
handsome-salesclerk-5432409/16/2023, 3:07 PM