release: Docker image has never published — no buildx builder, no GHCR login, upstream Dockerfile
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker, github-actions, typescript
调研方向
First resolve whether the project wants a container image. Read docs/RELEASING.md, packages/opencode/script/publish.ts, and packages/opencode/Dockerfile, then inspect the publish-npm job and validate with a local image build or beta tag. Done means the promised image publishes successfully end to end, or the Docker step, Dockerfile, and release documentation are removed consistently.
由索引模型根据 Issue 内容生成。
描述
docs/RELEASING.md says each release publishes ghcr.io/altimateai/altimate-code:<version>, but the Docker step in packages/opencode/script/publish.ts has failed on every release checked, from v0.10.0 through v0.12.4 (e.g. v0.12.4):
ERROR: failed to build: Multi-platform build is not supported for the docker driver.
Docker publish failed (non-fatal): …
The step is non-fatal and only logs, so releases stay green and no image is published.
The logged error is only the first of several problems:
- No multi-platform builder.
docker buildx build --platform linux/amd64,linux/arm64 --pushruns on the defaultdockerdriver. Needsdocker/setup-qemu-actionanddocker/setup-buildx-actionin thepublish-npmjob. - No registry login or permission. There is no
docker login ghcr.io, and the job has onlycontents: read. Needsdocker/login-actionwith the workflow token andpackages: write. The publish step'sGITHUB_TOKENenv is set toHOMEBREW_TAP_TOKEN, so the login has to be its own step. - The Dockerfile is upstream's.
packages/opencode/Dockerfilecopiesdist/opencode-linux-x64-baseline-musl/bin/opencodeanddist/opencode-linux-arm64-musl/bin/opencodeand usesENTRYPOINT ["opencode"]. This repo builds no musl binaries and names themaltimate-code, so the build fails even with 1 and 2 fixed. Needs a glibc base (e.g. Debian slim) copying thelinux-x64-baseline/linux-arm64altimate-codebinaries byTARGETARCH. - Never run end to end. Validate with a local image build (or a beta tag) before relying on it.
Decision needed first: whether a container image is wanted. If not, remove the step and the Dockerfile, and drop the docker pull lines from docs/RELEASING.md, which currently promise an image that does not exist.
- 主要语言
- TypeScript
- 星标
- 810
- 派生
- 121
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 88
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AltimateAI/altimate-code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
AltimateAI/altimate-code#1454 ·
维护者通常 1 天内回复
-
test: MCP tests fail when the developer's ~/.claude.json has MCP servers (HOME is not sandboxed)未关闭
难度 2/5 1-3 小时 新手友好度 78/100
AltimateAI/altimate-code#1386 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
AltimateAI/altimate-code#1384 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
AltimateAI/altimate-code#1323 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
AltimateAI/altimate-code#1288 ·
维护者通常 1 天内回复
查看 AltimateAI/altimate-code 的全部 Issue
相似的 Issue
-
bug priority: P2
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
wayfinder:task
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug customer-reported data-plane question Service Attention Storage
难度 2/5 1-3 小时 新手友好度 69/100
Azure/azure-rest-api-specs#47397 · 2 条评论 ·
维护者通常 1 天内回复
-
Claude thinking budget can shrink capped Haiku responses to 2,048 tokens可能已有人在做 @DavyMassoneto 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
diegosouzapw/OmniRoute#17109 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
paperclipai/paperclip#16785 ·
维护者通常 1 天内回复