minikube: Minikube tunnel hangs on Mac

minikube tunnel
❗  The service/ingress test-ingress requires privileged ports to be exposed: [80 443]
🔑  sudo permission will be asked for it.
🏃  Starting tunnel for service test-ingress.
Password:

After entering my password, there is no further output from the command.

Output of minikube logs logs.txt

minikube version: v1.24.0
commit: 76b94fb3c4e8ac5062daf70d60cf03ddcc0a741b

The ingress file I’m using

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: test.local
      http:
        paths:
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: server
                port:
                  number: 80
          - path: /
            pathType: Prefix
            backend:
              service:
                name: client
                port:
                  number: 80

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (3 by maintainers)

Most upvoted comments

Any update on this? I can’t get ingress to work in minikube on my M1 Mac. Same issue as described above. Can we reopen?

+19

NixBiks on Jan 28, 2022

Aha! This is an issue specifically with the docker driver, and it’s only an output issue. If you use a VM driver (like hyperkit for macOS), you’ll get the expected output in the documentation.

This stems from the fact that we need to do two discrete things to tunnel for a container driver (since it needs to route to 127.0.0.1) and for a VM driver.

We can potentially look into fixing this so that the output for both versions are similar, but the tunnel itself is working fine.

sharifelgamal on Dec 22, 2021

+1 Please provide some other solution/ alternatives for people who use docker.

harshraj22 on Nov 25, 2022

minikube tunnel is supposed to hang like that in your terminal. As long as the tunnel process is active, that terminal will look like it’s hanging. You can use that access in another terminal.

sharifelgamal on Dec 22, 2021

I am experiencing the same issue: there is no further output shown whereas the documentation states that there should be some output. The tunnel functionality itself is working, i.e. the external IP is exposed to the host system.

cptnnm on Nov 16, 2021