Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove listen [::]:80 from nginx/conf.d/default.conf #28486

Open
yxie2023 opened this issue Nov 18, 2024 · 0 comments
Open

remove listen [::]:80 from nginx/conf.d/default.conf #28486

yxie2023 opened this issue Nov 18, 2024 · 0 comments
Labels
A-Developer-Experience O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@yxie2023
Copy link

Steps to reproduce

docker fails to start on linux host with ipv6 disabled.

/docker-entrypoint.d/10-listen-on-ipv6-by-default.sh already adds this automatically if ipv6 is in fact enabled.

Outcome

docker run -it --rm docker.io/vectorim/element-web:latest

/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
2024/11/18 16:03:50 [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)

Operating system

Linux

Browser information

No response

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

Yes

@dosubot dosubot bot added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround labels Nov 18, 2024
@dbkr dbkr added S-Minor Impairs non-critical functionality or suitable workarounds exist A-Developer-Experience and removed S-Critical Prevents work, causes data loss and/or has no workaround labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Developer-Experience O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants