[VSCode] Empty chat panel in devcontainer

[WatchMeBakinWaffles]

Describe the bug
Tabby chat panel hangs and end up being empty when running in devcontainer.

First :

Few tens of seconds later :

I don't see any error in vscode tabby output.

Information about your version
Using tabby version : 0.20.0

Information about your GPU

Additional context
Running in devcontainer based on docker image debian:12.7-slim

[zwpaper]

Hello @WatchMeBakinWaffles, when running Tabby or other GPU-intensive applications in a container, you should use an NVIDIA-based image. Could you try using images such as nvidia/cuda:11.7.1-devel-ubuntu22.04?

Additionally, there is a state check on the System page in the Tabby admin homepage settings. Could you also try to verify the state of the models there?

[WatchMeBakinWaffles]

Hello @zwpaper. I will try next monday. But I'm still wondering, why would chat feature require nvidia based image while code completion is working correctly ?

[zwpaper]

@WatchMeBakinWaffles, you can check the model's functionality on the System page using a Debian-based image.

However, in most cases, an NVIDIA-based image is required for a GPU application to utilize GPU capabilities.

[WatchMeBakinWaffles]

Oh ok. I guess there is a misunderstanding there :

My VSCode extension is running inside a devcontainer whereas tabby server is actually running on my Ubuntu WSL (and clearly running on the GPU, I can confirm).

My issue is that the chat feature in VSC works well when VSC is running on host while it stops running when switching to devcontainer (and actually, the chat through web GUI is nice and smooth).

Additional infos:

Here is my run command:
tabby-serve='tabby serve --model DeepseekCoder-1.3B --chat-model Qwen2-1.5B-Instruct --device cuda --port 8089'

EDIT:

[zwpaper]

Hi @WatchMeBakinWaffles, apologies for the misunderstanding.

To clarify:

1. Both the web and VS Code chat function correctly when Tabby is running on the host machine.
2. Only the web chat operates properly, while the VS Code chat does not, when Tabby is running inside a devcontainer.

It appears this issue may be related to networking. Could you please try running the devcontainer with the host-network and see if that resolves the problem?