Docker deploy started failing today: failed to solve

[sergio]

Here’s the relevant part of my Dockerfile:

ARG ELIXIR_VERSION=1.14.5
ARG OTP_VERSION=25.0
ARG DEBIAN_VERSION=bullseye-20210902-slim

ARG BUILDER_IMAGE="hexpm/elixir:${ELIXIR_VERSION}-erlang-${OTP_VERSION}-debian-${DEBIAN_VERSION}"
ARG RUNNER_IMAGE="debian:${DEBIAN_VERSION}"

And here’s the image it’s pulling: https://registry.hub.docker.com/layers/hexpm/elixir/1.14.5-erlang-25.0-debian-bullseye-20210902-slim/images/sha256-36fd12427d71d7c949e283b7a52650d53afede95098e0c3f7c1a183014705870?context=explore

Here’s the error:

Sep 28 03:43:02 PM  #6 [internal] load metadata for docker.io/library/debian:bullseye-20210902-slim
Sep 28 03:43:02 PM  #6 ERROR: failed to authorize: failed to fetch oauth token: unexpected status: 503 Service Unavailable
Sep 28 03:43:02 PM  ------
Sep 28 03:43:02 PM   > [internal] load metadata for docker.io/library/debian:bullseye-20210902-slim:
Sep 28 03:43:02 PM  ------
Sep 28 03:43:02 PM  Dockerfile:79
Sep 28 03:43:02 PM  --------------------
Sep 28 03:43:02 PM    77 |     # start a new build stage so that the final image will only contain
Sep 28 03:43:02 PM    78 |     # the compiled release and other runtime necessities
Sep 28 03:43:02 PM    79 | >>> FROM ${RUNNER_IMAGE}
Sep 28 03:43:02 PM    80 |
Sep 28 03:43:02 PM    81 |     RUN apt-get update -y && apt-get install -y libstdc++6 openssl libncurses5 locales \
Sep 28 03:43:02 PM  --------------------
Sep 28 03:43:02 PM  error: failed to solve: debian:bullseye-20210902-slim: failed to authorize: failed to fetch oauth token: unexpected status: 503 Service Unavailable

Is this an issue with Docker services or a deprecation I need to fix myself in my codebase? Thanks!

[sergio]

On Render, it seemed like all I needed to do was “Clear build cache & deploy” to get it to function properly again.

Or maybe Docker fixed their URL issue?

[D4no0]

I start to think that using pipelines that use 90% of dependencies from a source you cannot control is dangerous, both in terms of outages and in terms of possible locks by vendor. I’ve had a similar issue today with not being able to fetch from hex.

Maybe it is time to break this cycle?

[pdgonzalez872]