bitwarden/setup Docker image seems to have issues with ipv6 enabled

[vipergts450]

Steps To Reproduce

1. Enable IPv6 support in daemon.json, ex:

  "ipv6": true,
  "fixed-cidr-v6": "fd00:1::/64"
}

2. Run ./bitwarden.sh update

Expected Result

Update process should complete normally.

Actual Result

bitwarden/setup:2025.1.2 container immediately exits with error: docker: Error response from daemon: Address already in use.

Screenshots or Videos

No response

Additional Context

As of 2025.1.2, I am unable to run bitwarden.sh update normaly. The image immediately crashes with docker: Error response from daemon: Address already in use. I was able to work around this bug by disabling IPv6 in my docker daemon.json file and then re-running the command. Having IPv6 enabled seemed to work fine until 2024.12.1, based on my server's update history. The server itself worked fine with IPv6, it just hasn't been able to update to the latest version, which I've narrowed down to the setup:2025.1.2 container specifically.

I am not sure how to track this regression further, but wanted to note it for the developers.

Build Version

2025.1.2

Environment

Self-Hosted

Environment Details

• Operating System: Debian 12 "bookworm" 6.1..0-30-amd64
• Environment: Docker

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[Greenderella]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!