The connection to the server 127.0.0.1:32768 was refused - did you specify the right host or port? #25391
-
What is happening?
Did I need to do anything else? Workflow-yaml
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It looks like your action is implemented as a docker container, but you started your kind cluster on the daemon on the VM host. Given the way docker networking is setup I don’t think you are going to be able to see that published port from inside a container. Also, your action will not have access to ~/.kube/config as that is the home path on the VM. If you run your tests using a bash script or an action implemented in JavaScript it should work. |
Beta Was this translation helpful? Give feedback.
-
Yes, for this specific case |
Beta Was this translation helpful? Give feedback.
Yes, for this specific case
We can use kind inside action using
kind get kubeconfig --internal >$HOME/.kube/config
it works for the version 0.7 of kind