NVIDIA / NVIDIA/NeMo-Retriever
[BUG]: Jupyter Notebook Unable to Communicate with Docker Compose Services
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3k
- Forks
- 349
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
Version
Latest
Which installation method(s) does this occur on?
Docker
Describe the bug.
@scothalverson @yulianazamora
Behavior
The Jupyter Notebook instance cannot establish network communication with any of the Docker Compose services due to being on a separate network.
Solution
To resolve this issue, the Jupyter Notebook container must be launched on the same network as the Docker Compose services. This can be achieved by using the --network flag with the docker run command to specify the Docker Compose network.
Minimum reproducible example
N/A
Relevant log output
N/A
Other/Misc.
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Docker Compose service network and the docker run command used to launch the Jupyter Notebook. Verify that the notebook container joins the Compose network and can communicate with each service; the issue is done when those connections work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, jupyter-notebook
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100