With self hosted , I have recently started getting the error: “The [certbot/certbot] container image used by this script is no longer associated with any containers. Would you like to purge it? (y/N)” when either starting Bitwarden or updating it even after following the Manual update instructionshttps://bitwarden.com/help/certificates/ . Is anyone else getting this? OS is Debian 12 and using Docker’s repo.
Edit: It looks like this prompt was added in commit 79ef3523 in GitHub - bitwarden/self-host: Bitwarden's self-hosted release repository , although I don’t think filtering on ancestor=certbot/certbot is the correct approach for this as when using the normal instructions for setting up certbot, I don’t think anything gets associated to the base certbot docker image.
yep same issue here, my daily updates were breaking due to this change because some ■■■■■■■ thought it would be a good idea to ask questions in the middle of a script that has never asked questions before, and they didn’t even have the decency to give us a flag to skip it. FAIL!
Piping a “y” character to the bitwarden.sh script seems to have worked around the issue for me. Annoying that they didn’t provide a “force” or “quiet” flag for script operation.
