github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #12448] Docker ENV pull models and ensure availability on container_healthy status #70330

New Issue
Closed
opened 2026-05-04 21:08:46 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-04 21:08:46 -05:00
Owner
Copy Link

Originally created by @uvulpos on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12448

To run my application tests with the AI in a pipeline, I have to pull models first. So, I could make a docker exec call to pull them, or, I would like to define them as a variable, and it gets pulled and stored in a volume automatically. The advantage of this is, that my testing setup then is unified in my CI and my local system and if I have to deploy Ollama in a Kubernetes environment, everything is already ready because everything is defined as code

  • Docker Env can pull models on startup
  • Docker auto-pull is documented on how to store models in docker volume / Kubernetes PVC
  • Docker pull can be verified by docker healthcheck

References: #12262

Originally created by @uvulpos on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12448 To run my application tests with the AI in a pipeline, I have to pull models first. So, I could make a docker exec call to pull them, or, I would like to define them as a variable, and it gets pulled and stored in a volume automatically. The advantage of this is, that my testing setup then is unified in my CI and my local system and if I have to deploy Ollama in a Kubernetes environment, everything is already ready because everything is defined as code - [ ] Docker Env can pull models on startup - [ ] Docker auto-pull is documented on how to store models in docker volume / Kubernetes PVC - [ ] Docker pull can be verified by docker healthcheck References: #12262
GiteaMirror added the feature request label 2026-05-04 21:08:46 -05:00
GiteaMirror commented 2026-05-04 21:08:53 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Sep 29, 2025):

https://github.com/ollama/ollama/issues/7046#issuecomment-2383792234

<!-- gh-comment-id:3348871698 --> @rick-github commented on GitHub (Sep 29, 2025): https://github.com/ollama/ollama/issues/7046#issuecomment-2383792234
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#70330
Delete Branch "%!s()"

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?