You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating namespace 'redacted-6k0bp8t5zl'...>>> kubectl create namespace redacted-6k0bp8t5zlThe connection to the server 127.0.0.1:42511 was refused - did you specify the right host or port?========================================================================================================================........................................................................................................................==> Events of namespace redacted-6k0bp8t5zl........................................................................................................................>>> kubectl get events --output wide --namespace redacted-6k0bp8t5zlThe connection to the server 127.0.0.1:42511 was refused - did you specify the right host or port?Error printing details: Error waiting for process: exit status 1>>> kubectl get pods --no-headers --namespace redacted-6k0bp8t5zl --selector --output jsonpath={.items[*].metadata.name}Error printing logs: Error running process: exit status 1Deleting release 'redacted-6k0bp8t5zl'...
kubectl in the docker container is not able to communicate to kind cluster.
What you expected to happen:
It is expected to run ct install in docker container with k8s cluster on the host machine.
Is this a request for help?: No.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report
Version of Helm and Kubernetes:
What happened:
From README, the following command returns error.
kubectl
in the docker container is not able to communicate tokind
cluster.What you expected to happen:
It is expected to run
ct install
in docker container with k8s cluster on the host machine.How to reproduce it:
kind create cluster
ct.yaml
docker run -it --workdir=/data --volume ~/.kube/config:/root/.kube/config:ro --volume $(pwd):/data quay.io/helmpack/chart-testing:v3.5.0 ct install
The text was updated successfully, but these errors were encountered: