Unable to sign in into Github (copilot)

[s0170071]

Is there an existing issue for this?

• [x] I have searched the existing issues

OS/Web Information

• Web Browser: Firefox
• Local OS:
• W10
• Remote OS: 12 (bookworm)
• Remote Architecture: RPI5
• code-server --version: latest

Steps to Reproduce

Use code server as docker container with this compose file:

code-server:
    image: lscr.io/linuxserver/code-server:latest
    mem_limit: 1000m
    container_name: "code-server"
    environment:
      - PUID=${OHUID}
      - PGID=${OHGID}
      - TZ=Europe/Berlin
      - SUDO_PASSWORD=
      - EXTENSIONS_GALLERY={"serviceUrl":"https://marketplace.visualstudio.com/_apis/public/gallery","itemUrl":"https://marketplace.visualstudio.com/items"}
      - DEFAULT_WORKSPACE=/config/workspace

    volumes:
      - /opt/openhab:/config/workspace
      - /opt/code-server:/config
    ports:
      - "8444:8443"
      - "8082:8080"
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost:8443 || exit 1"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 20s
    depends_on:
      mosquitto:
        condition: service_started

Then install the extension from the list of extensions. Then try to sign in by clicking on the copilot icon. Then clicking on "continue with Github"

There will be an immediate error message "Failed to sign in to GitHub. Would you like to try again?" before there is even the user/password prompt.

The same works nicely with native vsc on W10

Expected

Login successful

Actual

There will be an immediate error message "Failed to sign in to GitHub. Would you like to try again?" before there is even the user/password prompt.

Logs

please advise how to do this with a docker container.

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• [ ] I am using a secure context.

Notes

I get the secure context message a lot, however, so far everything has been working and I have no clue how to solve this on a RPI5 running docker.