Installation Method
Docker (multi-container - docker-compose)
What is the issue?
I am trying to isolate the open-notebook container from the network entirely, so that it only can communicate with the Ollama LLM within the same network (it will run on a server with a limited network access).
To simulate this, I create a docker network within docker-compose file.
The problem is, when I try to startup the service it fails to start the API (frontend is fine) with the errors from pip whl.
But when the first startup of the container is done with the opened network (e.g. internal: false), then all the next startups are fine. Looks like it installs something within the first run in the container.
Shouldn't all the dependencies be built inside the docker image, so that the startup does not modify it?
Logs
× Failed to download `virtualenv==20.35.4`
├─▶ Failed to fetch:
│ `https://files.pythonhosted.org/packages/79/0c/c05523fa3181fdf0c9c52a6ba91a23fbf3246cc095f26f6516f9c60e6771/virtualenv-20.35.4-py3-none-any.whl`
├─▶ Request failed after 3 retries
├─▶ error sending request for url
│ (https://files.pythonhosted.org/packages/79/0c/c05523fa3181fdf0c9c52a6ba91a23fbf3246cc095f26f6516f9c60e6771/virtualenv-20.35.4-py3-none-any.whl)
├─▶ client error (Connect)
├─▶ dns error
╰─▶ failed to lookup address information: Try again
help: `virtualenv` (v20.35.4) was included because `open-notebook:dev`
Docker Compose Configuration
networks:
my_network_isolated:
driver: bridge
internal: true
open_notebook:
container_name: open_notebook
networks:
- my_network_isolated
image: lfnovo/open_notebook:1.2.1
volumes:
- ./notebook_data:/app/data
restart: alwaysEnvironment File
System Information
No response
Additional Context
No response
Pre-submission Checklist
Installation Method
Docker (multi-container - docker-compose)
What is the issue?
I am trying to isolate the open-notebook container from the network entirely, so that it only can communicate with the Ollama LLM within the same network (it will run on a server with a limited network access).
To simulate this, I create a docker network within docker-compose file.
The problem is, when I try to startup the service it fails to start the API (frontend is fine) with the errors from pip whl.
But when the first startup of the container is done with the opened network (e.g. internal: false), then all the next startups are fine. Looks like it installs something within the first run in the container.
Shouldn't all the dependencies be built inside the docker image, so that the startup does not modify it?
Logs
Docker Compose Configuration
Environment File
System Information
No response
Additional Context
No response
Pre-submission Checklist