Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

release: Docker image has never published — no buildx builder, no GHCR login, upstream Dockerfile

Aberta
  • Algo errado?
#1,389 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, github-actions, typescript
Domínio
cloud, devops, release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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:

  1. No multi-platform builder. docker buildx build --platform linux/amd64,linux/arm64 --push runs on the default docker driver. Needs docker/setup-qemu-action and docker/setup-buildx-action in the publish-npm job.
  2. No registry login or permission. There is no docker login ghcr.io, and the job has only contents: read. Needs docker/login-action with the workflow token and packages: write. The publish step's GITHUB_TOKEN env is set to HOMEBREW_TAP_TOKEN, so the login has to be its own step.
  3. The Dockerfile is upstream's. packages/opencode/Dockerfile copies dist/opencode-linux-x64-baseline-musl/bin/opencode and dist/opencode-linux-arm64-musl/bin/opencode and uses ENTRYPOINT ["opencode"]. This repo builds no musl binaries and names them altimate-code, so the build fails even with 1 and 2 fixed. Needs a glibc base (e.g. Debian slim) copying the linux-x64-baseline / linux-arm64 altimate-code binaries by TARGETARCH.
  4. 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.

Linguagem predominante
TypeScript
Estrelas
812
Forks
123
Merge médio
1d 16h
PRs com merge (30d)
83

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de AltimateAI/altimate-code

Todas as issues de AltimateAI/altimate-code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.