Hi @Th_o_Vy_Le_Nguy_n,
I am trying to complete the ungraded lab 2 of C4_W2.
My platform is Windows 11 with WSL2.
I am running Linux version of Minikube and started with the following in a wsl shell: minikube start --mount=True --mount-string=“/var/tmp:/var/tmp” --vm-driver=docker
When I progressed the end of first part of the lab to the following: curl -d ‘{“instances”: [1.0, 2.0, 5.0]}’ -X POST http://192.168.49.2:30001/v1/models/half_plus_two:predict
I get error such as : curl: (28) Failed to connect to 192.168.49.2 port 30001 after 132587ms: Connection timed out
I saw your earlier replies to another user seemed to have similar connection problem and wonder would you be kind enough to look at it and advise. Many thanks in advance.
Hi @BHTan ,
When you said you’re using the Minikube Linux version. Did you mean you installed it with WSL? If that is the case, the network might be limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly. Also, running minikube on Linux with the Docker driver will result in no tunnel being created.
You try switching to Docker or try these steps to fix minikube:
Hi @Th_o_Vy_Le_Nguy_n, something is wrong with my local PC set up. May I clarify the following is the correct steps?
0. Docker was installed from previous lab in C4_W1.
Turn on Windows Features for Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux (see below).
I had restarted the whole installation from fresh without VirtualBox and docker’s.
Also, most important, I edited the deployment.yaml to increase the memory.limit to 6000M (6G as per your suggestion).
I ran a separate Ubuntu window “minikube service tf-serving-service” to open a tunnel to the service.
I managed to run the curl command successful this time and saw the results returned by the model finally! I also completed the rest of the Lab 2 exercise successfully.
Most important 2 things I learned are : (1) how to use ‘kubectl describe all’ and to debug why found the container (tf-serving) got terminated/recreated multiple times - due to memory constraint problem and prompted me to edit the deployment.yaml. (2) given my local Windows11+wsl2+ubuntu setup, I must ran “minikube service tf-serving-service” to have minikube open a tunnel for me to connect the service server for submitting the json inputs.