Proxy Container Error

AI & Data Science NVIDIA AI Workbench
1

I’ve just installed NVIDIA AI Workbench onto a Windows 11, which went through successfully.

I am following the Basic Quickstart example.
When I click on “Open Jupyterlab” button, I receive the error:
“Proxy Container Error: The proxy container is not currently running. Please restart local to resolve this issue.”

image
image1323×726 50.8 KB

I can’t find where to go to “restart local” as everything seems to be running fine. My docker service on Windows is running and I don’t see any other daemons that need to be started/restarted.

Can someone please help?

2

Hi, thanks for reaching out. Try this:

  1. Close out of AI Workbench
  2. On the system application tray, expand the options and look for a gray AI Workbench icon. Right click and select “quit”. On windows it should look like this.
    image
  3. Reopen AI Workbench and select the local location again.
3

Unfortunately, it’s not working for me, even after restarting the workbench as you described. What else can I do, to get the Jupyterlab working?

5

Hi, thanks for reaching out. Sorry to hear about this.

First, can you verify you are running the latest version of AI Workbench? You can run nvwb version in the CLI and/or WSL distro and/or you can right click the desktop icon and select About.

Can you also create a support log (nvwb support create-bundle in the CLI) and email the zip file to aiworkbench-support@nvidia.com? This will help provide more information to help us pinpoint the source of the issue you are running into. Thanks!

You can find the generated zip file in the .nvwb folder.

6

It seems I stumbled on the same problem. Also on the cli I do not get any further information. Restarting the context as suggested didn’t help.

:~/nvidia-workbench/NVIDIA-workbench-example-sdxl-customization$ nvwb start --container

 X Starting container

 An error occurred:
 failed to start container because the reverse proxy container is not running. Try deactivating and reactivating the context by running: `nvwb deactivate --shutdown`, followed by `nvwb activate <context>`

Did any solution meanwhile occur?