4 months ago
scheduling build on Metal builder "builder-fsjlwt"
scheduling build on Metal builder "builder-fsjlwt"
[snapshot] received sha256:d62b2ad14a6697d85ab0346524c2683a178711ef50f62f4720b554152adb5870 md5:219843a11af05d4fbfe78153b36e66e9
receiving snapshot130.7 MB9.8s
found 'Dockerfile' at 'Dockerfile'
analyzing snapshot130.7 MB1.7s
uploading snapshot130.7 MB4.4s
fetched snapshot sha256:d62b2ad14a6697d85ab0346524c2683a178711ef50f62f4720b554152adb5870 (137 MB bytes)
fetching snapshot130.7 MB3.6s
unpacking archive172.2 MB2.0s
internal
load build definition from Dockerfile
0ms
internal
load metadata for docker.io/library/eclipse-temurin:21-jdk-jammy
14m 44s
internal
load metadata for docker.io/library/maven:3.9.6-eclipse-temurin-21
1 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Your build logs show the "load metadata" step for the Docker Hub base images (eclipse-temurin and maven) took over 14 minutes, which indicates slow responses from Docker Hub during image resolution. Retrying the deployment typically resolves this, and you can check Docker Hub's status page for any ongoing incidents.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago