Uh oh!
There was an error while loading. Please reload this page.
listen on both ipv4 and ipv6 even when running container as root - #216
Conversation
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
LinuxServer-CI
commented
Jun 17, 2026
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
ozraru
commented
Jul 2, 2026
@aptalca (author of #179) Hello, sorry to bother you - this is actually my first contribution to a linuxserver repo, so I'm not fully sure of the usual process here. This PR follows the same reasoning as #179 - it just extends the same fix to the root-run case, which was missed originally. Could one of you take a look when you have a moment? Thanks! |
Description:
Updated
/root/etc/s6-overlay/s6-rc.d/svc-code-server/runto change--bind-addrfrom0.0.0.0:8443to[::]:8443when the container is executed as the root user.Also added the corresponding changelog entry in
readme-vars.yml(andREADME.md).Benefits of this PR and context:
In a #179, the container was configured to listen on both IPv4 and IPv6. However, that change seems to have been missed or not fully applied for the root execution path. This PR corrects it so that
code-serverproperly binds to[::]:8443regardless of whether it's running as root or a non-root user.How Has This Been Tested?
Test A: dual stack
compose.yaml
localhost:8443resulted in aCONNECTION_RESETerror.localhost:8443connects successfully.Test B: IPv4 only
compose.yaml
localhost:8443connects successfully.Source / References:
#179