astro-cli icon indicating copy to clipboard operation
astro-cli copied to clipboard

Astro CLI not working with IPV4, no IPV6 available

Open PierceLovesee opened this issue 11 months ago • 0 comments

Describe the bug

I am trying to get Astro CLI working on a fresh install of Debian 12.

What CLI Version did you experience this bug? Astro CLI Version

Astro CLI Version: 1.33.0

However, I am unable to start the dev environment. I believe I need to whitelist the IPV4 addresses for the quay.io registrys. Can those be provided?

astro dev start
#0 building with "default" instance using docker driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 214B done
#1 DONE 0.0s

#2 [internal] load metadata for quay.io/astronomer/astro-runtime:12.2.0
#2 ERROR: failed to do request: Head "https://quay.io/v2/astronomer/astro-runtime/manifests/12.2.0": dial tcp [2600:1f18:483:cf01:dde4:4c4f:a6f8:7576]:443: connect: network is unreachable
------
 > [internal] load metadata for quay.io/astronomer/astro-runtime:12.2.0:
------
Dockerfile:1
--------------------
   1 | >>> FROM quay.io/astronomer/astro-runtime:12.2.0
   2 |     
   3 |     # RUN python -m venv .venv_dbt && source .venv_dbt/bin/activate && \
--------------------
ERROR: failed to solve: quay.io/astronomer/astro-runtime:12.2.0: failed to resolve source metadata for quay.io/astronomer/astro-runtime:12.2.0: failed to do request: Head "https://quay.io/v2/astronomer/astro-runtime/manifests/12.2.0": dial tcp [2600:1f18:483:cf01:dde4:4c4f:a6f8:7576]:443: connect: network is unreachable

Error: an error was encountered while building the image, see the build logs for details

This CLI bug is related to which Astronomer Platform?

  • [ ] Astro
  • [ ] Software
  • [ ] None/Unknown

What Operating System is the above CLI installed on?

Debian 12

I intentionally do not want IPV6 networking enabled. I think I need the ipv4 addresses to whitelist quay.io.

🪜 Steps To Reproduce

📸 Screenshots

PierceLovesee avatar Feb 17 '25 23:02 PierceLovesee