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

Issue with starting the Minikube with VPN, Docker driver and MacOs #12512

Open
dlminvestments opened this issue Sep 18, 2021 · 12 comments
Open
Labels
cause/vpn issues caused by VPN's kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@dlminvestments
Copy link

Steps to reproduce the issue:

1.complete return from Minikube start command from terminal. Im guessing I should reset the kernel that is used for docker or report the issue to apple. If possible can tech support troubleshoot so that the popup window displays to reset kernel factory settings back to default to initiate a restart for docker. Heres the response I receive from the Minikube start command ==>(check line 2)

  1. minikube start
    😄 minikube v1.23.0 on Darwin 11.5.1 (arm64)
    ✨ Using the docker driver based on existing profile
    👍 Starting control plane node minikube in cluster minikube
    🚜 Pulling base image ...
    🤷 docker "minikube" container is missing, will recreate.
    🔥 Creating docker container (CPUs=4, Memory=1973MB) ...
    🤦 StartHost failed, but will try again: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c -d /var/lib: exit status 125
    stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c' locally
docker: Error response from daemon: Get "https://gcr.io/v2/": Bad Request.
See 'docker run --help'.

🤷 docker "minikube" container is missing, will recreate.
🔥 Creating docker container (CPUs=4, Memory=1973MB) ...
😿 Failed to start docker container. Running "minikube delete" may fix it: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c' locally
docker: Error response from daemon: Get "https://gcr.io/v2/": Bad Request.
See 'docker run --help'.

❌ Exiting due to GUEST_PROVISION: Failed to start host: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c' locally
docker: Error response from daemon: Get "https://gcr.io/v2/": Bad Request.
See 'docker run --help'.

  1. Ive tried deleting and replacing the docker file to restart docker but receive the same response when trying to restart Minikube. need some additional tech support to troubleshoot this issue...

Run minikube logs --file=logs.txt and drag and drop the log file into this issue

Full output of failed command if not minikube start:

@yxxhero
Copy link
Member

yxxhero commented Sep 19, 2021

@dlminvestments in china?

@dlminvestments
Copy link
Author

eastern time zone

@yxxhero
Copy link
Member

yxxhero commented Sep 20, 2021

@dlminvestments try docker pull gcr.io/k8s-minikube/kicbase:v0.0.26

@dlminvestments
Copy link
Author

I have the image on docker but still refuses connect ==> Error response from daemon: Get "https://gcr.io/v2/": Bad Request
I've tried pretty much everything I've installed daemon tools it fails to connect the registry I tried running vms through virtual box its refusing connects there. the only thing I have access to are self built processes that run through my self develop software. all other applications are failing. the step I haven't done yet is report the kernel issue to apple so that it can reset but I don't know how to do that if the screen doesn't display. I need to reset the kernel to pull images to at least install Minikube

@yxxhero
Copy link
Member

yxxhero commented Sep 20, 2021

@dlminvestments try recreate minikube by the follow cmd:

# prune images

minikube delete
docker system prune
minikube start

@dlminvestments
Copy link
Author

same output ==> 😄 minikube v1.23.1 on Darwin 11.6 (arm64)
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🤷 docker "minikube" container is missing, will recreate.
🔥 Creating docker container (CPUs=4, Memory=1988MB) ...
🤦 StartHost failed, but will try again: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.26@sha256:d4aa14fbdc3a28a60632c24af937329ec787b02c89983c6f5498d346860a848c' locally
docker: Error response from daemon: Get "https://gcr.io/v2/": Bad Request.
See 'docker run --help'.

@fsbaraglia
Copy link

Hi, @dlminvestments,
which hardware are you using? because I see from your output Darwin 11.6 (arm64).

@dlminvestments
Copy link
Author

Correct I tried installing Ubuntu and centos 9 but the virtual machine has been disabled. Access is being refused so I’m using a local hardware stored on my hard drive

@spowelljr
Copy link
Member

Hi @dlminvestments, are you behind a VPN or firewall? Is this a corporate machine or a personal machine?

@spowelljr spowelljr added triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Oct 13, 2021
@dlminvestments
Copy link
Author

I actually have both a vpn and a firewall setup. Currently it's a virtual machine but the IT department is talking with vendors and myself to incorporate the security system for corporate. I work as a freelance & I'm looking for contractual work from companies that need inbuilt or added layers of security for their Infrastructure & private servers

@medyagh
Copy link
Member

medyagh commented Oct 20, 2021

@dlminvestments is there way we could replicate your VPN setup ?

@sharifelgamal is interested in making VPN experience with minikube better but we dont have a way to replicate the issue, is if you are willing, please hit him up on slack or here to share info, so maybe there is something minikube could do

meanwhile can u plz attach this file to this issue

minikube logs --file=logs.txt

@medyagh medyagh changed the title Issue with starting the Minikube container for Docker Issue with starting the Minikube with VPN and docker driver Oct 20, 2021
@medyagh medyagh changed the title Issue with starting the Minikube with VPN and docker driver Issue with starting the Minikube with VPN, Docker driver and MacOs Oct 20, 2021
@medyagh medyagh added the cause/vpn issues caused by VPN's label Oct 20, 2021
@dlminvestments
Copy link
Author

The VPN was setup through Cloudflare. I can do two things I can either grant you access to teams.cloudflare.com or I can securely allow you to connect through an open port. You can use my subnet mask and IP address which then would request or ask to allow the connect to pass through a tcp.
7A1041C2-D626-4A72-88CD-A26CD40E97CD

here’s a link to slack & we can discuss more details there

https://join.slack.com/t/dlm-vm1/shared_invite/zt-xgd9kdxy-6ie1YVol3XPvPqLw1tkLAA

I unlocked the firewall so I believe it would allow automatic connections. You can try again a popup window would show and I can allow the connection through a tcp if you have a proxy to peer the connection. but yeah I unlocked the firewall manually so give it a try if that doesn't work then message. I have other policies in place my DNS and network policy so just message me on slack.

@spowelljr spowelljr removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Nov 3, 2021
@sharifelgamal sharifelgamal added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed kind/support Categorizes issue or PR as a support question. labels Dec 15, 2021
@spowelljr spowelljr added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 16, 2022
@sharifelgamal sharifelgamal added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 16, 2022
@spowelljr spowelljr added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/vpn issues caused by VPN's kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

6 participants