2 months ago
My backend used to deploy successfully, but now it can’t deploy anymore — it keeps giving me a health check error.
2 Replies
2 months ago
I need help
2 months ago
[Region: us-east4]
=========================
Using Detected Dockerfile
=========================
context: b3q2-b0WV
internal
load build definition from Dockerfile
0ms
internal
load metadata for docker.io/library/eclipse-temurin:17-jre-jammy
104ms
internal
load metadata for docker.io/library/maven:3.9.3-eclipse-temurin-17
108ms
internal
load .dockerignore
0ms
stage-1
12ms
internal
load build context
0ms
builder
14ms
stage-1
WORKDIR /app cached
0ms
stage-1
RUN addgroup --system javauser && adduser --system --group javauser cached
0ms
stage-1
RUN apt-get update && apt-get install -y curl iproute2 && rm -rf /var/lib/apt/lists/* cached
0ms
stage-1
COPY --from=builder /build/target/app.jar /app/app.jar cached
0ms
builder
RUN mvn clean package -DskipTests -DfinalName=app cached
0ms
builder
COPY src/ src/ cached
0ms
builder
RUN mvn dependency:go-offline cached
0ms
builder
COPY pom.xml . cached
0ms
builder
WORKDIR /build cached
0ms
stage-1
RUN chown -R javauser:javauser /app cached
0ms
exporting to image
6s
auth
sharing credentials for production-us-east4-eqdc4a.railway-registry.com
0ms
importing to docker
3s
Build time: 6.64 seconds
==================== Starting Healthcheck ====================
Path: /healthz
Retry window: 5m0s
Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Attempt #2 failed with service unavailable. Continuing to retry for 4m38s
Attempt #3 failed with service unavailable. Continuing to retry for 4m34s
Attempt #4 failed with service unavailable. Continuing to retry for 4m26s
Attempt #5 failed with service unavailable. Continuing to retry for 4m15s
Attempt #6 failed with service unavailable. Continuing to retry for 3m49s
Attempt #7 failed with service unavailable. Continuing to retry for 3m19s
Attempt #8 failed with service unavailable. Continuing to retry for 2m45s
Attempt #9 failed with service unavailable. Continuing to retry for 2m5s
Attempt #10 failed with service unavailable. Continuing to retry for 1m32s
Attempt #11 failed with service unavailable. Continuing to retry for 1m0s
Attempt #12 failed with service unavailable. Continuing to retry for 30s
Attempt #13 failed with service unavailable. Continuing to retry for 0s
1/1 replicas never became healthy!
Healthcheck failed!