`docker model` CLI detects "Docker Engine" on Docker Desktop for Windows and tries to start standalone runner (port 12434 conflict)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the bundled plugin at C:\Program Files\Docker\cli-plugins\docker-model.exe and reproduce the issue with docker model status against the desktop-linux context. Check how the plugin distinguishes Docker Desktop's runner from a standalone runner and selects the runner image, using the working http://localhost:12434/engines/v1/models endpoint as a reference. Done means the model commands use the available Desktop runner without the port conflict or an inappropriate CUDA image.
由索引模型根据 Issue 内容生成。
描述
Environment
- Windows, Docker Desktop 4.93.0 (240920), context
desktop-linux docker model version: Client v1.2.6 / Server v1.2.8, Engine: Docker Engine- Plugin path (from
docker info):C:\Program Files\Docker\cli-plugins\docker-model.exe - CPU: Intel (no NVIDIA GPU)
Problem
Every docker model command (status, ls, list, run) pulls docker/model-runner:latest-cuda and tries to start a standalone docker-model-runner container, which fails because Docker Desktop's Model Runner already listens on 127.0.0.1:12434 (owned by com.docker.backend.exe):
unable to initialize standalone model runner: unable to initialize standalone model runner container: failed to start container docker-model-runner: Error response from daemon: ports are not available: exposing port TCP 127.0.0.1:12434 -> 127.0.0.1:0: listen tcp4 127.0.0.1:12434: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
Evidence the Desktop runner works
curl http://localhost:12434/engines/v1/models returns {"object":"list","data":[]}.
Already tried
- Machine reboot
docker desktop disable model-runner+docker desktop enable model-runner --tcp=12434- With the Desktop runner disabled, the standalone runner fails binding
172.17.0.1:12434("can't bind on the specified endpoint") - No
MODEL_RUNNER_HOST/DOCKER_HOSTenv vars set
Notable
- CLI reports
Engine: Docker Enginewhiledocker versionreportsServer: Docker Desktop 4.93.0 (240920). - CLI pulls the
latest-cudaimage on a machine without an NVIDIA GPU. - Client/server version mismatch (1.2.6 vs 1.2.8).
Possibly related: #377 (closed). The fix there was removing a stale plugin from ~/.docker/cli-plugins, but here the resolved plugin is the one bundled with Docker Desktop.
- 主要语言
- Go
- 星标
- 659
- 派生
- 159
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 13
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
docker/model-runner 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
docker/model-runner#1073 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 68/100
docker/model-runner#1063 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
docker/model-runner#1059 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
docker/model-runner#1058 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
docker/model-runner#1056 · 1 条评论 ·
维护者通常 1 天内回复
查看 docker/model-runner 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 69/100
aws/amazon-ecs-agent#5177 ·
维护者通常 2 天内回复
-
release-followup
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
kind/bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
apache/rocketmq-dashboard#7292 ·
维护者通常 3 天内回复
-
[Bug]: Deleting an MCP proxy leaves its API keys in the gateway's memory and in the policy engine未关闭Aspect/API Aspect/Other Severity/Minor Type/Bug
难度 2/5 1-3 小时 新手友好度 83/100
wso2/api-platform#3852 ·
维护者通常 1 天内回复