Hi @Amit_Srivastava, welcome to discourse! Can you provide the OS and shell that you are running this on? It looks like the the bind mount didn’t work as expected. Did you successfully cloned the serving repo in the /tmp/tfserving directory?
Hola Sergio!
To get the lab running please use a WSL2 shell instead of Powershell. You can type in the Windows search bar for wsl or bash and one of these shells should be available since you have WSL2 already installed.
I just tried to run WSL at lower memory levels (~55%), however, WSL did close immediately. So problem of WSL instability was not related to high memory usage.
Then: I did solve the problem with WSL closing immediately reviewing this link and running the following line in PowerShell: C:> wsl.exe --set-default Ubuntu.18-04
However, I got an error message in WSL when trying to run the command to spin up a container to serve the model under TFS.
I uninstalled and installed Docker again.
Now WSL runs ok
the command spins up a container (see screen 1)
However, some error happens, and it enters in a loop asking for something (see screen 2)
When tried to get an inference it got an error (see screen 3)
I would appreciate your comments.
Thanks in advance.
Best
Sergio
Great! One trick to make sure that you have the correct path is to navigate to the root directory where you cloned the repo and type the pwd command. It should return the current working directory. So if you cloned it under /mnt/tmp/tfserving instead, then the new source argument would be /mnt/tmp/tfserving/serving/tensorflow_serving/servables/tensorflow/testdata/saved_model_half_plus_two_cpu.
Hi Chris,
I just did check the path, and it seems ok. See the screenshot below.
However, the problem is still there. In the docker dashboard, the image appears running now. However, the same message appears, I mean as it shows in the previous screenshot.