Fix Dockerfile: use :latest for both stages #21

Merged

ldraney merged 1 commit from fix-dockerfile-build-tag into main

2026-05-10 19:06:50 +00:00

ldraney commented

2026-05-10 19:06:09 +00:00

Owner

Summary

The ruby-arch pipeline only pushes :latest (which is the build stage with compilers). The :build tag referenced in the Dockerfile doesn't exist, breaking Docker builds.

Changes

FROM pal-e/ruby-arch:build AS build → FROM pal-e/ruby-arch:latest AS build

Test Plan

docker build succeeds locally with external Harbor URL
App boots and health check passes

Review Checklist

One-line fix
Temporary — proper fix is to push separate :base/:build tags from the pipeline

Follow-up needed: update ruby-arch Woodpecker pipeline to push both :base and :build tags via Kaniko --target.

## Summary The ruby-arch pipeline only pushes `:latest` (which is the build stage with compilers). The `:build` tag referenced in the Dockerfile doesn't exist, breaking Docker builds. ## Changes - `FROM pal-e/ruby-arch:build AS build` → `FROM pal-e/ruby-arch:latest AS build` ## Test Plan - [ ] `docker build` succeeds locally with external Harbor URL - [ ] App boots and health check passes ## Review Checklist - [x] One-line fix - [x] Temporary — proper fix is to push separate :base/:build tags from the pipeline ## Related Notes Follow-up needed: update ruby-arch Woodpecker pipeline to push both `:base` and `:build` tags via Kaniko `--target`.

ldraney added 1 commit

2026-05-10 19:06:09 +00:00

Fix Dockerfile: use :latest for both stages 29c0562137

The ruby-arch pipeline only pushes :latest (which is the build stage).
The :build tag doesn't exist. Use :latest for both until the pipeline
is updated to push separate :base and :build tags.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>