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
If you use Docker containers with IPV6 disabled, mainsail is not able to start.
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: ipv6 not available
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2025/02/02 18:41:05 [emerg] 1#1: socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Maybe is a good idea use ENV and a Docker entrypoint script. For example:
#!/bin/sh
CONFIG_FILE="/etc/nginx/conf.d/default.conf"
if [ "$IPV6" = "disabled" ]; then
echo "IPv6 is disabled. Removing IPv6 listen directive from Nginx config."
sed -i '/listen \[::\]:80;/d' "$CONFIG_FILE"
fi
Mainsail Version:
edge
Browser:
Firefox
Device:
Desktop PC
Operating System:
Windows
What happened?
If you use Docker containers with IPV6 disabled, mainsail is not able to start.
Maybe because PR https://github.com/mainsail-crew/mainsail/pull/2030/files
What did you expect to happen instead?
Maybe is a good idea use ENV and a Docker entrypoint script. For example:
Then, modify the Dockerfile:
And finally run with IPV6 ENV flag to disable IPV6:
How to reproduce this bug?
You can create a Docker network without IPV6 support, just dont use the flag --ipv6
And attach this network to your container. Im my case, im using this ipvlan network:
Additional information:
No response
The text was updated successfully, but these errors were encountered: