Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tunneling not working: Windows 11; Docker on Windows; kubernetes / minikube #13296

Closed
dsosale opened this issue Jan 4, 2022 · 4 comments
Closed
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@dsosale
Copy link

dsosale commented Jan 4, 2022

Tunneling not working for the following configuration.
Please advise if there is a fix:

Windows: Windows 11 Pro
Windows for docker: Docker Desktop 4.3.2 (72729)
Kubernetes: v1.23.0
Minikube: minikube version: v1.24.0

Command sequence:

minikube start --driver=docker

minikube mount C:/kubepgms/pods/resource/test/:/data/configs

minikube ssh
ls -la /data/configs/
(shows test1.yaml)

docker pull nginx:mainline-alpine

docker run -i -t --name nginx-mainline -p 80:80 nginx:mainline-alpine

If you navigate to http://localhost you will get a welcome page.

kubectl create deployment hello-node --image=nginx:mainline-alpine
kubectl get deployments
kubectl get pods
kubectl get events
kubectl expose deployment hello-node --type=LoadBalancer --port=8080

minikube service hello-node

Gives error: ! Because you are using a Docker driver on windows, the terminal needs to be open to run it.

(does not work even if I paste the http address directly into chrome).

C:/kubepgms/pods/resource/test/test1.yaml:
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:

  • name: nginx
    image: nginx:1.14.2
    ports:
    • containerPort: 80
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 4, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 5, 2022
@spowelljr
Copy link
Member

Hi @dsosale, thanks for reporting your issue with minikube. I tried to replicate what you were experience and I believe it's related to the image you're using itself. Could you try using the commands below and let me know if that works for you.

kubectl create deployment balanced --image=k8s.gcr.io/echoserver:1.4
kubectl expose deployment balanced --type=LoadBalancer --port=8080
minikube tunnel

Then in your browser open http://127.0.0.1:8080/

That works for me, but when I try using the image nginx:mainline-alpine instead of k8s.gcr.io/echoserver:1.4 it doesn't work for me, so I think it's related to the image itself.

@spowelljr spowelljr added kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it. labels May 25, 2022
@spowelljr
Copy link
Member

Hi @dsosale, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants