Closed tiberio87 closed 6 months ago
I found the problem. I had ipv6 disabled in GRUB, once reactivated it works. How can I make it work with ipv6 disabled?
I wonder if this is related to recent changes in Docker 26.1 with IPv6 (cc @robmry)
I wonder if this is related to recent changes in Docker 26.1 with IPv6 (cc @robmry)
One change we made is to not-disable IPv6 on the loopback interface just because a container isn't (yet) connected to an IPv6-enabled network. But, if the kernel hasn't added a ::1
to the loopback interface in the first place, we take that as a signal that IPv6 is disabled on the host, or for the container using --sysctl net.ipv6.conf.all.disable_ipv6=1
, or similar. We shouldn't be doing anything to try to enable IPv6 at that point.
Is there anything in the nginx config that's explicitly enabling IPv6 or asking it to listen on ::
? From a glance at the project's Dockerfile, I think this is nginx installed in an alpine container ... I just tried that with IPv6 disabled in the container, and nginx started, even with listen [::]:80 default_server;
left in its default config - but perhaps disabling IPv6 in the kernel would be different.
This is related to the nginx software. I submitted a pull request to resolve the problem. There's no reason to support IPV6 in the first place. IPV6 support was never properly tested and added to rTorrent. IPV4 is required to use the docker container.
Ah right that makes sense and indeed no need to enable IPv6 within the nginx conf explicitly.
Support guidelines
I've found a bug and checked that ...
Description
I'm getting an nginx error
Expected behaviour
working as it should
Actual behaviour
totalt breakdown
Steps to reproduce
update to latest version
Docker info
Docker Compose config
Logs
Additional info
No response