Fix docker-compose.yaml #2073
Fix docker-compose.yaml #2073
Conversation
There was a problem hiding this comment.
Please revert the changes I have marked for you. On the other hand, to solve this problem, what we have to do is to retry the initial connection to ollama. E.g. https://stackoverflow.com/questions/50246304/using-python-decorators-to-retry-request
| private-gpt-ollama: | ||
| image: ${PGPT_IMAGE:-zylonai/private-gpt}:${PGPT_TAG:-0.6.2}-ollama # x-release-please-version | ||
| user: root | ||
| image: ${PGPT_IMAGE:-zylonai/private-gpt}:${PGPT_TAG:-0.6.2}-ollama |
There was a problem hiding this comment.
Please don't remove # x-release-please-version
| private-gpt-llamacpp-cpu: | ||
| image: ${PGPT_IMAGE:-zylonai/private-gpt}:${PGPT_TAG:-0.6.2}-llamacpp-cpu # x-release-please-version | ||
| image: ${PGPT_IMAGE:-zylonai/private-gpt}:${PGPT_TAG:-0.6.2}-llamacpp-cpu |
There was a problem hiding this comment.
Please don't remove # x-release-please-version
|
|
||
| # Traefik reverse proxy for the Ollama service | ||
| # This will route requests to the Ollama service based on the profile. | ||
| ollama: | ||
| traefik: |
There was a problem hiding this comment.
If you change service name, you cannot connect to ollama using http://ollama:11434
| # Ollama service for the CPU mode | ||
| ollama-cpu: | ||
| # Ollama service | ||
| ollama: |
There was a problem hiding this comment.
Please go back to ollama-cpu. Traeffik will route each request to these children service
|
We close this PR since the changes are not valid. They don't fix anything, they just prevent them from happening. Fixed at: #2059 |
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
This change solves the problem described in issue #2071