a month ago
I'm running a Dockerfile build that has worked in the past that uses the Alpine CDN. The CDN is accessible right now, but not from within the Dockerfile builder?
I tried once, opened the link manually (which worked, so alpine cdn is not down), then tried again. Both attempts show the same error in the build logs.
Note: I just tried now after typing this and it appears to be back alive. I'm still posting this for information that something was flaky, but it seems that all's fine now and this is resolved.
For internal debugging, see deployment id da7afc19-1c96-476f-a50a-8088da886df6.
From the build logs:
[production 3/7] RUN apk add py3-pip && python3 -m venv venv && ./venv/bin/pip3 install sanic
WARNING: updating and opening https://dl-cdn.alpinelinux.org/alpine/v3.23/main/x86_64/APKINDEX.tar.gz: HTTP 502: Bad Gateway
WARNING: updating and opening https://dl-cdn.alpinelinux.org/alpine/v3.23/community/x86_64/APKINDEX.tar.gz: HTTP 502: Bad Gateway
ERROR: unable to select packages:
py3-pip (no such package):
required by: world[py3-pip]
1 Replies
a month ago
Thanks for the report. This was a transient connectivity issue reaching the Alpine CDN from the build environment, and since it resolved on its own, no further action is needed on your end.
Status changed to Awaiting User Response Railway • 29 days ago
Status changed to Solved glingy • 29 days ago