[Bug]: Installer fails on ipv6

[ogdakke]

Description

Hi! I am very new to self hosting and server configuration in general, so bare with me here.

I got a ipv6-only server from Hetzner, and the first thing I did was I tried to run the installation script found on coolify docs, and, in the end, with the -vvv -trace flags I got this error:
Error response from daemon: Get https://ghcr.io/v2/: dial tcp 140.82.121.33:443: connect: network is unreachable.
This led me to a discussion on https://community.home-assistant.io/t/unable-to-pull-images-from-ghcr-io/448349 where there was mentions of ip6-caused errors.
With no flags, curl was just outputting curl: (7) Couldn't connect to server

Fixed by getting a ipv4 address for my server. I am aware that this is probably not a coolify issue, but might prove usefol for folks to take a look at this.

Minimal Reproduction (if possible, example repository)

• Deploy a cloud instance on Hetzner/elsewhere with ipv6 only IP address
• run the install script

Exception or Error

No response

Version

v4.0.0-beta.183

[Codomic]

Would love to use an ipv6 only server from Hetzner but also running into the same issue on my Rocky Linux instance. Hopefully ipv6 support for the automatic installer can be added in the future.

[DanielOberlechner]

Hi I tried the exact same thing today also on a Hetzner server with only ipv6 ip address and I wondered why the installation process failed.

This issue is still relevant.

The reason I don't have an ipv4 address is that I have to pay extra to get one.

Is there a chance that this issue is gonna get resolved in the near future?

Kind regards,
Daniel

[andrasbacsai]

In the next version, there will be an option to use docker.io only images for Coolify, so that means IPv6 only servers could be used: https://coolify.io/docs/knowledge-base/custom-docker-registry