Error calling kind script

[jacobdotcosta]

bash <(curl -s -L https://raw.githubusercontent.com/snowdrop/k8s-infra/main/kind/kind.sh)                                                                                                  INT ✘  18:01:36

/dev/fd/13: line 877: [: -v: unary operator expected
/dev/fd/13: line 881: [: -v: unary operator expected
/dev/fd/13: line 885: [: -v: unary operator expected
/dev/fd/13: line 889: [: ==: unary operator expected

Welcome to our

   _____                                  _
  / ____|                                | |
 | (___    _ __     ___   __      __   __| |  _ __    ___    _ __
  \___ \  | '_ \   / _ \  \ \ /\ / /  / _  | |  __|  / _ \  | \ _ \
  ____) | | | | | | (_) |  \ V  V /  | (_| | | |    | (_) | | |_) |
 |_____/  |_| |_|  \___/    \_/\_/    \__,_| |_|     \___/  |  __/
                                                            | |
                                                            |_|
Script to create/delete a Kubernetes cluster using kind like a :
- (secured) docker container registry
- ingress controller (nginx, kourier)

/dev/fd/13: line 225: [: ==: unary operator expected
✔ Pre requisites check passed!

[aureamunoz]

I have also a problem with it even if it moves forward and creates the cluster, I have a problem regarding the internal registry. This is the output:

./kind.sh install --delete-kind-cluster                                                                                                                                        125 ✘  18s  15:15:24 
./kind.sh: line 877: [: -v: unary operator expected
./kind.sh: line 881: [: -v: unary operator expected
./kind.sh: line 885: [: -v: unary operator expected
./kind.sh: line 889: [: -v: unary operator expected

Welcome to our
                                                                   
   _____                                  _                        
  / ____|                                | |                       
 | (___    _ __     ___   __      __   __| |  _ __    ___    _ __  
  \___ \  | '_ \   / _ \  \ \ /\ / /  / _  | |  __|  / _ \  | \ _ \ 
  ____) | | | | | | (_) |  \ V  V /  | (_| | | |    | (_) | | |_) |
 |_____/  |_| |_|  \___/    \_/\_/    \__,_| |_|     \___/  |  __/ 
                                                            | |    
                                                            |_|    
Script to create/delete a Kubernetes cluster using kind like a : 
- (secured) docker container registry
- ingress controller (nginx, kourier)

✔ Pre requisites check passed!
! Deleting Kind cluster...
✔ Removing kind cluster (kind)...
✔ Removing kind registry container...
✔ ...done!
! Checking if kind cluster exists...
Creating cluster "kind" ...
DEBUG: docker/images.go:58] Image: kindest/node:v1.26.3@sha256:61b92f38dff6ccc29969e7aa154d34e38b89443af1a2c14e6cfbd2df6419c66f present locally
 ✓ Ensuring node image (kindest/node:v1.26.3) 🖼
 ✓ Preparing nodes 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Thanks for using kind! 😊
configmap/local-registry-hosting created
716710aa3615603f3c3c7a5147013d833d0eecc8f846e5f8a8a88612c56c0ed1
docker: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:5000 -> 0.0.0.0:0: listen tcp 0.0.0.0:5000: bind: address already in use.

I don't have any process in port 5000:

docker ps                                                                                                                                                                          ✔  15:40:41 
CONTAINER ID   IMAGE                  COMMAND                  CREATED          STATUS          PORTS                                                                                    NAMES
4f7a65b0e0b1   kindest/node:v1.26.3   "/usr/local/bin/entr…"   10 minutes ago   Up 10 minutes   127.0.0.1:49938->6443/tcp                                                                kind-control-plane
198bf6a1d061   postgres:14            "docker-entrypoint.s…"   24 hours ago     Up 24 hours     0.0.0.0:61511->5432/tcp                                                                  wizardly_moore
111ce8c8ed02   consul                 "docker-entrypoint.s…"   7 days ago       Up 7 days       8300-8302/tcp, 8500/tcp, 8301-8302/udp, 8600/tcp, 8600/udp                               fox
28393f45e1a2   consul                 "docker-entrypoint.s…"   7 days ago       Up 7 days       8300-8302/tcp, 8600/tcp, 8301-8302/udp, 0.0.0.0:8500->8500/tcp, 0.0.0.0:8600->8600/udp   badger

I think the problem is the use of 0.0.0.0in the script for the registry, shouldn't be 127.0.0.1?

[aureamunoz]

The problem is that it is not getting to expose the ports, so the registry container is created but not running: