Since the use of ghcr.io i cannot update bitwarden on linux/arm64/v8 platform

[Exifs]

Self-host installation scripts issue

• I understand this repository only tracks self-host installation scripts and any other issues should be reported in bitwarden/server

Steps To Reproduce

try to deploy any bitwarden self-host docker image on a raspberry pi using the ghcr.io repo

Expected Result

I should be able to update my bitwarden installation on linux/arm64/v8 processors even if the image repository has changed

Actual Result

Error response from daemon: image with reference ghcr.io/bitwarden/self-host:2025.2.1-beta was found but its platform (linux/amd64) does not match the specified platform (linux/arm64/v8)

Screenshots or Videos

No response

Additional Context

No response

Build Version

bitwarden/self-host:2025.2.1-beta

Environment

Self-Hosted

Environment Details

raspberry pi 4b

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.

[rmcdowell-bitwarden]

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!

[Exifs]

Hi there,

It seems that I did not give enough information to reproduce.

The problem is happening when a change my docker-compose file et try to update my container. with the new ghcr.io repository.

The old docker-compose that was working is :

version: "3.8"

services:
  bitwarden:
    depends_on:
      - db
    env_file:
      - settings.env
    image: bitwarden/self-host:2025.2.1-beta
    restart: always
    ports:
      - "9080:8080"
      - "8443:8443"
    volumes:
      - bitwarden:/etc/bitwarden
      - logs:/var/log/bitwarden
  db:
    environment:
      POSTGRES_USER: "MY_USER"
      POSTGRES_PASSWORD: "MY_DB_PASSWORD"
      POSTGRES_DB: "DB_NAME"
    image: postgres:14
    restart: always
    volumes:
      - data:/var/lib/postgresql/data

volumes:
  bitwarden:
  logs:
  data:

I updated it to :

version: "3.8"

services:
  bitwarden:
    depends_on:
      - db
    env_file:
      - settings.env
    image: ghcr.io/bitwarden/self-host:2025.2.1-beta
    restart: always
    ports:
      - "9080:8080"
      - "8443:8443"
    volumes:
      - bitwarden:/etc/bitwarden
      - logs:/var/log/bitwarden
  db:
    environment:
      POSTGRES_USER: "MY_USER"
      POSTGRES_PASSWORD: "MY_DB_PASSWORD"
      POSTGRES_DB: "DB_NAME"
    image: postgres:14
    restart: always
    volumes:
      - data:/var/lib/postgresql/data

volumes:
  bitwarden:
  logs:
  data:

Now the bitwarden service is not starting with only this error in docker compose logs :

474f85255aaf_bitwarden-bitwarden-1  | exec /entrypoint.sh: exec format error
474f85255aaf_bitwarden-bitwarden-1 exited with code 255

I tried to add a platform im my docker compose file so it is forced to download the arm image (added platform: linux/arm64/v8 in the bitwarden service). Now it does not pull the image with the error message given in the issue :

Error response from daemon: image with reference ghcr.io/bitwarden/self-host:2025.2.1-beta was found but its platform (linux/amd64) does not match the specified platform (linux/arm64/v8)

I don't see any build made for ARM in the ghcr.io repository. And the error message is confirming it.

@rmcdowell-bitwarden How did you manage to get it working on arm processor ?

[niccokunzmann]

Arm64 servers become increasingly popular. I.e. Hetzner in Germany provides several locations based on this architecture - at lower costs. Creating a docker buildx with linux/arm64/v8 included would be really nice, so that Bitwarden can be deployed on this architecture.

It appears that the first container to migrate to buildx is ghcr.io/bitwarden/setup - I am unsure where the source code is.