You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the docker container when ipv6 is disabled by the kernel gives: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol).
Specifically ipv6 was disabled by sudo grubby --args=ipv6.disable=1 --update-kernel=ALL on Fedora 39.
Expected Behavior
It should work just like when ipv6 is enabled.
Steps To Reproduce
Disable ipv6 via sudo grubby --args=ipv6.disable=1 --update-kernel=ALL on Fedora 39 and in docker daemon via {"ipv6": false} in /etc/docker/daemon.json then reboot
docker compose up snapdrop given the compose file below
Environment
- OS: Fedora 39
- How docker service was installed: sudo dnf install docker
You'll need to manually update the /config/nginx/site-confs/default.conf to remove the IPv6 listeners on the server blocks, we can't sensibly change our shipped default confs to accomodate users who are inexplicably still disabling IPv6 in (nearly) 2024.
Is there an existing issue for this?
Current Behavior
Running the docker container when ipv6 is disabled by the kernel gives:
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
.Specifically ipv6 was disabled by
sudo grubby --args=ipv6.disable=1 --update-kernel=ALL
on Fedora 39.Expected Behavior
It should work just like when ipv6 is enabled.
Steps To Reproduce
sudo grubby --args=ipv6.disable=1 --update-kernel=ALL
on Fedora 39 and in docker daemon via{"ipv6": false}
in/etc/docker/daemon.json
then rebootdocker compose up snapdrop
given the compose file belowEnvironment
CPU architecture
x86-64
Docker creation
From my
docker-compose.yml
:Where
${CONFIG}/snapdrop
is a valid path on my host systemContainer logs
The text was updated successfully, but these errors were encountered: