Issue Report: Build Succeeds but Deployment Fails

Project: h2o-llmstudio

Environment: production

Project ID: 450751db-d723-493a-b36a-7a3a4383095c

Problem

Two consecutive deployments complete the Docker build successfully but fail during the image push/registry phase, preventing the service from deploying.

Failed Deployments

Deployment ID: 3be4eb1a-4ea6-40f4-97c5-bf56b64f31c0

Triggered: 2026-06-17 19:47:43 UTC

Status: FAILED (BUILD_IMAGE stage)

Build completed: 19:51:41 UTC

Deployment ID: 7bf7f616-ce53-4a5f-a25d-9f57b1af5242

Triggered: 2026-06-17 19:53:28 UTC

Status: FAILED (BUILD_IMAGE stage)

Build completed: 19:54:23 UTC

Build Evidence

Both deployments show identical successful build output:

All 18 Dockerfile steps completed successfully

Image exported to Docker format

Container image digest: sha256:9fc9b915967493730ab0fc38bf54d98ab8d8d037515df56b6f99d14aa3145ce9

Config digest: sha256:6e8a1e8f72b522b24f592749386e65f9979284578a915c66c15b4e210ad90607

Error Message

Failed to build an image. Please check the build logs for more details.

The build logs show no errors—the image builds and exports successfully. The failure occurs after the build completes, likely during image push to the registry.

Code Changes

The Dockerfile was updated to use the public python:3.10-slim base image instead of a private AWS ECR image. This change is present in the repo and builds without issues.

Expected Behavior

After successful image export, the deployment should push the image to the registry and proceed to the deployment phase.

Actual Behavior

Deployment marked as FAILED despite successful build completion.

This appears to be an infrastructure/registry issue on Railway's side, not a code or configuration problem.