cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(deploy): make bundled Ollama opt-in to avoid duplicate container #2

Merged
cesnimda merged 1 commits from fix/ollama-no-duplicate into main 2026-07-03 15:06:23 +02:00
Conversation 0 Commits 1 Files Changed 2
+11 -3
cesnimda commented 2026-07-03 15:00:34 +02:00
Owner
Copy Link
Copy Source

The compose file shipped its own ollama service, so 'docker compose pull'
during deploy re-downloaded the Ollama image and a deploy that starts the
AI stack would spin up a second Ollama alongside an existing/shared one.

  • ollama service moved behind a 'bundled-ollama' compose profile, so it is
    excluded from the default pull/up (no duplicate, no re-download)
  • ai-service no longer depends_on ollama and is documented to point at a
    shared instance via OLLAMA_BASE_URL (e.g. http://:11435)
  • deploy.sh no longer names ollama in 'compose up'

To run a self-contained Ollama: docker compose --profile bundled-ollama up

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com

The compose file shipped its own ollama service, so 'docker compose pull' during deploy re-downloaded the Ollama image and a deploy that starts the AI stack would spin up a second Ollama alongside an existing/shared one. - ollama service moved behind a 'bundled-ollama' compose profile, so it is excluded from the default pull/up (no duplicate, no re-download) - ai-service no longer depends_on ollama and is documented to point at a shared instance via OLLAMA_BASE_URL (e.g. http://<host>:11435) - deploy.sh no longer names ollama in 'compose up' To run a self-contained Ollama: docker compose --profile bundled-ollama up Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cesnimda added 1 commit 2026-07-03 15:00:34 +02:00
fix(deploy): make bundled Ollama opt-in to avoid duplicate container
CI and Deploy / test (pull_request) Successful in 2m4s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details
e1e508988a 
The compose file shipped its own ollama service, so 'docker compose pull'
during deploy re-downloaded the Ollama image and a deploy that starts the
AI stack would spin up a second Ollama alongside an existing/shared one.

- ollama service moved behind a 'bundled-ollama' compose profile, so it is
  excluded from the default pull/up (no duplicate, no re-download)
- ai-service no longer depends_on ollama and is documented to point at a
  shared instance via OLLAMA_BASE_URL (e.g. http://<host>:11435)
- deploy.sh no longer names ollama in 'compose up'

To run a self-contained Ollama: docker compose --profile bundled-ollama up

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cesnimda merged commit 31373be841 into main 2026-07-03 15:06:23 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cesnimda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cesnimda/jobtrackingapp#2
Delete Branch "fix/ollama-no-duplicate"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?