Rocket Bind Error?

Help
1

I’ve been using Vaultwarden via docker-compose for a while now, but I’m now having an issue I have not experienced before. I’m unable to find anyone else reporting having this same issue on the forum or in the Github Issues.

The docker container just constantly restarts, and docker logs vaultwarden just keeps repeating this, so I’m unsure of what to try:

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.36.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

Error: Rocket.
[CAUSE] Bind(
    Os {
        code: 13,
        kind: PermissionDenied,
        message: "Permission denied",
    },
)

Any ideas on how to troubleshoot this?

This is my current docker-compose.yml:

version: '3'

services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: always
    environment:
      #DOMAIN: "https://vaultwarden.mydomain.com"
      ADMIN_TOKEN: "<my-admin-token>"
      SIGNUPS_ALLOWED: "false"
      INVITATIONS_ALLOWED: "false"
      SENDS_ALLOWED: "false"
      SIGNUPS_VERIFY: "false"
      ORG_CREATION_USERS: "none"
    ports:
      - 8080:80
    volumes:
      - ./srv/vw-data:/data
2

I’m still unable to determine what was wrong, but I was able to move all of my data from the Ubuntu 20.04 with ESM server I was using to a new server running Alpine 3.24, and everything is now working as it had been.

Perhaps the docker versions were the issue, but it had been working fine for over 2 years now and still continued to work after each upgrade.

  • Docker version on Ubuntu 20.04 ESM:
    • docker --version
      • Docker version 28.1.1, build 4eba377
    • docker-compose --version
      • docker-compose version 1.25.0, build unknown
  • Docker version on Alpine 3.23:
    • docker --version
      • Docker version 29.5.3, build d1c06ef6b41d88d76866aea43c246cd7c63d04fa
    • docker-compose --version
      • Docker Compose version v5.1.4

How shall I mark this? “Workaround” instead of “Solved”?

3

That version is very outdated. I am not sure if that is the culprit but that would probably be the first thing I would test. Alternatively you might have your docker setup somehow configured to run in rootless mode?

The other workaround that should work would be to e.g. set ROCKET_PORT: 8000 and change the port mapping to8080:8000 so it does not try to bind to a port lower than 1024 (this should be allowed in newer docker versions but since you are using a very old docker-compose I think this might interfere somehow.)