Stuck on container "Starting"

[LufoX11]

Steps To Reproduce

1. ./bitwarden.sh start

Expected Result

All containers to start.

Actual Result

All containers stuck in "starting".

bitwarden@ip-172-31-33-233:/opt/bitwarden$ ./bitwarden.sh start
 _     _ _                         _
| |__ (_) |___      ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Open source password management solutions
Copyright 2015-2025, 8bit Solutions LLC
https://bitwarden.com, https://github.com/bitwarden

===================================================

bitwarden.sh version 2025.1.4
Docker version 24.0.2, build cb74dfc
Docker Compose version v2.18.1

[+] Pulling 11/11
 ✔ identity Pulled        0.7s 
 ✔ web Pulled             0.7s 
 ✔ admin Pulled           0.7s 
 ✔ api Pulled             0.7s 
 ✔ icons Pulled           0.6s 
 ✔ events Pulled          0.7s 
 ✔ nginx Pulled           0.7s 
 ✔ mssql Pulled           0.7s 
 ✔ attachments Pulled     0.7s 
 ✔ notifications Pulled   0.7s 
 ✔ sso Pulled             0.7s 
[+] Building 0.0s (0/0)                                                                                                                                                         
[+] Running 0/9
 ⠧ Container bitwarden-attachments    Starting    81.8s 
 ⠧ Container bitwarden-icons          Starting    81.8s 
 ⠧ Container bitwarden-web            Starting    81.8s 
 ⠧ Container bitwarden-api            Starting    81.8s 
 ⠧ Container bitwarden-notifications  Starting    81.8s 
 ⠧ Container bitwarden-events         Starting    81.8s 
 ⠧ Container bitwarden-sso            Starting    81.8s 
 ⠧ Container bitwarden-mssql          Starting    81.8s 
 ⠧ Container bitwarden-identity       Starting    81.8s 

Screenshots or Videos

No response

Additional Context

There are no errors in screen or logs.

I have a current plan subcription (Premium), which I enabled on September 2024. I followed instructions in https://bitwarden.com/help/self-host-an-organization/ and added globalSettings__enableCloudCommunication=true in global.override.env. License and everything was working until last update.

I've tried "update", "updatedb", "updateself" but nothing changed.

Did something change lately? Maybe I must whitelist a new connection port in AWS?

Build Version

2025.1.4

Environment

Self-Hosted

Environment Details

EC2 instance (AWS) running Ubuntu 18.04.

bitwarden.sh version 2025.1.4
Docker version 24.0.2, build cb74dfc
Docker Compose version v2.18.1

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.

[Neonwarden]

Hi there,

I attempted to reproduce your issue and was unable to do so. Can you try updating the Docker version? Bitwarden currently only supports version 26+. https://bitwarden.com/help/install-on-premise-linux/#system-specifications

We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, please write us back using our “Contact Support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

[LufoX11]

It ended up being something related to cache or dirty docker images/volumes.

Solution for me was to regenerate the docker environment:

# docker system prune -a
$ ./bitwarden.sh rebuild
$ ./bitwarden.sh start

So even docker is obsolete for the latest versions, it still works.

Thanks