[BUG] vscode-server does not start if IPv6 is not available

Start by reproducing the failure with the provided Docker service configuration on a host with IPv6 disabled, then trace the code-server container startup path that attempts to bind to :::8443. Done means the latest code-server image starts successfully without IPv6 while retaining its expected access behavior; verify with the container logs and the same reproduction steps.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The container fails to start on a host where IPv6 has been disabled.

Expected Behavior

The container should start.

Steps To Reproduce

1. Disable IPv6 on the Docker host
2. Start the container with the latest code-server image
3. The container fails to start due to being unable to bind to ":::8443"

Environment

- OS: Debian 11
- How docker service was installed: Official Debian package

CPU architecture

x86-64

Docker creation

services:
  code-server:
    image: linuxserver/code-server:4.127.0
    container_name: code-server
    hostname: code-server
    restart: unless-stopped
    volumes:
      - code-server:/config
      - code-server-data:/data
    environment:
      TZ: Europe/Berlin
      HASHED_PASSWORD: '<redacted>'
      DEFAULT_WORKSPACE: /data
    labels:
      traefik.enable: true
      traefik.http.routers.code-server.rule: "Host(`code-server.example.com`)"

Container logs

[2026-07-04T15:39:49.962Z] info  code-server 4.127.0 1e6ed874e3138141a5636f6e0dbe8570aa6cd001
[2026-07-04T15:39:49.963Z] info  Using user-data-dir /config/data
[2026-07-04T15:39:49.977Z] error listen EAFNOSUPPORT: address family not supported :::8443