Replies: 1 comment
-
|
After some investigation I've found that proxy environment variables are not exported to user profiles - and thus network access for user is prevented. I can tell to LLM in prompt (when I expect that any package need to be installed) to apply these specific proxy variables and in such case installation with pip is successful. However there is still problem with packages installation during container start i.e. with OPEN_TERMINAL_PIP_PACKAGES variable. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
I'm running latest open-terminal in docker on Ubuntu 24.04 with proxy for Internet access. When I start it with single user configuration then all actions scheduled by LLM that require Internet (like pip installing new packages) work correctly. But as soon I use multiuser functionality:
podman run -p 8010:8000 -d --name open-terminal --restart unless-stopped --env "http_proxy=http://192.168.1.1:3128" --env "https_proxy=http://192.168.1.1:3128" --env "no_proxy=host.docker.internal" --env "OPEN_TERMINAL_MULTI_USER=true" --env "OPEN_TERMINAL_API_KEY=xxxxxxx" -v /mnt/data/ai/open-terminal:/home ghcr.io/open-webui/open-terminal:latest
then every such action returns connectivity problem messages. Even installation of Python packages at container startup using OPEN_TERMINAL_PIP_PACKAGES environment variable fails due to 'Failed to establish a new connection: [Errno 101] Network is unreachable'.
What am I missing or doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions