bitwarden
run.sh pauses if the certbot container image doesn't have an ancestor
Self-host installation scripts issue
- [x] I understand this repository only tracks self-host installation scripts and any other issues should be reported in bitwarden/server
Steps To Reproduce
"bitwarden.sh start" or "bitwarden.sh restart"
Expected Result
bitwarden.sh start should start Bitwarden without waiting for any prompts
Actual Result
It now always displays the following prompt: "The [certbot/certbot] container image used by this script is no longer associated with any containers. Would you like to purge it? (y/N)" regardless of whether I select y or n.
Screenshots or Videos
No response
Additional Context
On my system I only have one certbot image: certbot/certbot:latest and it looks like this new problem is caused by the recently added Cleanup-Certbot function in run.sh (commit: 79ef352369f08c71a700f6cc7bd03dc932e1e4d8)
I also redid "Manually update a Let's Encrypt certificate" at https://bitwarden.com/help/certificates/ to see if that would help and it didn't seem to.
Build Version
v2025.12.1
Environment
Self-Hosted
Environment Details
Debian 12 with Docker repo: https://download.docker.com/linux/debian
Issue Tracking Info
- [x] 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.
