hyperkit | A toolkit for embedding hypervisor capabilities | Infrastructure Automation library

When starting up minikube with hyperkit driver on MacOS, is there a way to specify the ip address prefix used by the minikube VM? The default ip address of minikube hyperkit VM is 192.168.64.0/24. This address range conflicts with the office ip address and I would like to change it. However, I did not find documentation on how to config that.

Docker Desktop supports moving the VM Image that it uses onto another drive if needed. On my Mac Mini (2018) I have moved it to an external SSD in order to enlarge it more than the internal storage would have allowed.

The external SSD was named "Extra Space", which (ironically) became a problem when I also tried to use the SSD for other non-Docker development and discovered that some of the Ruby Gems I am using have problems with spaces in path names.

I decided that I would have to rename the drive to "ExtraSpace" (without the "extra" space), but then Docker was not able to find its VM Image. I was unable to use the built-in location chooser ("Preferences" -> "Resources" -> "Advanced" -> "Disk Image Location") because that tool assumes that it is moving the image from one location to another but in my case the image is not being moved, only the path to the existing image is changing.

I looked through the Docker configuration in ~/Library/Containers/com.docker.desktop/ and found the path to the image in Library/Containers/com.docker.docker/Data/vms/0/hyperkit.json. I tried changing it there, but Docker Desktop would not start.

In the error logs, I found lots of messages like this:

I am trying to use Ingress in minikube by minikube addons enable ingress. However, currently Ingress cannot be used with minikube when the driver is docker on macOS based on this issue ticket.

So I turn to use hyperkit or virtualbox as driver. One image that need to be pulled when enabling Ingress is k8s.gcr.io/ingress-nginx/controller:v0.44.0. However, k8s.gcr.io is blocked in my current location.

So I try to use a VPN in global mode for my computer. However, I met this issue that hyperkit is unable to access k8s.gcr.io when the VPN is in use.

Then I found this document https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/

My VPN is listening at 127.0.0.1:1087, I set

Dear StackOverflow community!

I am trying to run the https://github.com/GoogleCloudPlatform/microservices-demo locally on minikube, so I am following their development guide: https://github.com/GoogleCloudPlatform/microservices-demo/blob/master/docs/development-guide.md

After I successfully set up minikube (using virtualbox driver, but I tried also hyperkit, however the results were the same) and execute skaffold run, after some time it will end up with following error:

Playing around with K8 and ingress in local minikube setup. Creating ingress from yaml file in networking.k8s.io/v1 api version fails. See below output. Executing

I have installed kube-prometheus-stack as a dependency in my helm chart on a local Docker for Mac Kubernetes cluster v1.19.7.

The myrelease-name-prometheus-node-exporter service is failing with errors received from the node-exporter daemonset after installation of the helm chart for kube-prometheus-stack is installed. This is installed in a Docker Desktop for Mac Kubernetes Cluster environment.

release-name-prometheus-node-exporter daemonset error log

I'm running a local minikube cluster as of version v1.15.1 with Kubernetes version v1.19.4 and Docker 19.03.13. Local hypervisor is hyperkit.

I'm unable to update the deployment with a new image version from Docker Hub. I'm using imagePullPolicy: Always. The Image is clearly updated on Docker Hub. I pulled it locally and ran the image outside the kubernetes cluster to test that.

I tried the following methods to update within the cluster without success:

1. Deleting the pod and letting it be restarted by kubernetes (because the deployment specifies one replica)
2. Deleting the whole deployment via kubectl delete deployment service-frontend-voting
3. Doing a rolling update via kubectl rollout restart deployment service-frontend-voting, kubectl get pods shows that the pod is only seconds old. But still, old image.
4. Updating the deployment via kubectl set image deployment/service-frontend-voting service-frontend-voting=starax/service-frontend-voting:latest
5. Pushing same image to new tag on docker hub and doing steps 1-3 switching :latest to :next and vice versa
6. Using only :latest or imagePullPolicy: Always in the deployment spec, because apparently Kubernetes should pull the image if either of those are specified.

None of that methods have updated the image. What am I missing here?

The application itself is a simple VueJS app. The wanted change is the backend-url. Using environment variables with a production vue-js app is not trivial and therefor skipped here.

Deployment.yaml for reference:

I am running minikube v1.15.1 on MacOS and installed helm v3.4.1. I run helm install elasticsearch elastic/elasticsearch --set resources.requests.memory=2Gi --set resources.limits.memory=4Gi --set replicas=1 to install elasticsearch on k8s cluster. The pod elasticsearch-master-0 is deployed but it is in pending status.

When I run kubectl describe pod elasticsearch-master-0 it gives me below warning:

On a mac, docker utilizes HyperKit in order to create a LinuxKit VM. This means, for example, among other things, that I cannot see any of the image layers that are pulled down for a given container in places like /var/lib/docker, since the VM controls all of that.

Is there a way to actually get a shell on that VM to be able to do that sort of introspection?