Suggestion about model reinstall-runner
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 651
- Forks
- 155
- PR merge metrics
- No merged PRs in 30d
Description
I hoped reinstall-runner would just take the old runner settings and transfer them to a possible updated runner image.
Instead it dropped all former settings:
- host got reseted to 127.0.0.1 from 0.0.0.0
( i guess same would happen if you would choose a different port) - host restart policy got changed back from --restart until-stopped
- a docker network connect "my-personal-backend-network" docker-model-runner got reseted to only have the default bridge.
I would love to see a model update-runner specially if you need a new version from llama.cpp or a change in behaivior for the reinstall-runner.
Contributor guide
No contributing guide indexed for this repository
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 tracing the reinstall-runner entry point and how it handles the existing runner settings when replacing the runner image. Compare its behavior for the host, restart policy, port, and Docker network, then review how a possible update-runner command should preserve those settings while supporting a changed llama.cpp version or behavior. Done means the requested settings survive the runner update and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100