Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#1,389 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, typescript
Área
cloud, devops, release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
810
Forks
121
Merge medio
1 d 9 h
PR fusionados (30 d)
88

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AltimateAI/altimate-code

Todos los issues de AltimateAI/altimate-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.