I’m here because I don’t understand what’s going on my setup.
I installed a fresh Bitwarden setup on an Ubuntu VM. All went well and I can start using Bitwarden as my primary password manager.
Tonight, I decided to restard my VM to check if everything is ok after a restart. And it was… Except I don’t see my containers running with the docker ps command. But my vault is accessible with my phone and my computer. I don’t understand why no container are running (or saw here).
If I try to run ./bitwarden.sh start (or any other command) I get this error
I’m very new to docker, containers and all these things, I’m still trying to understand myself. This time I don’t understand what’s the issue. I searched on internet (didn’t ask IA but why ?) and find someone with the same error but didn’t manage to understand what he has done to repair the error.
I found some traces of the containers using systemctl status but can someone help me understand all of that ?
It LOOKS like you may have skipped this part of the setup:
bitwarden must be ran and executed on a specific directory with a made for this purpose user, and the rights to it. the error you get is that its a read only directory, so thats probably whats happening.
create bitwarden user. set the permissions, dont install or run as root, but the bitwarden user
can you double check the owner, and permissions of the bitwarden folder?
Hello, I’ve done everything in the procedure to deploy Bitwarden. At first glance everything worked as discribed in the documentation.
If you check my first screenshot, you can see that I opened bitwarden session on my machine bitwarden and I changed directory to /opt/bitwarden and launch bitwarden.sh start .
I already checked the permissions and bitwarden user is owner of the /opt/bitwarden directory. I had the idea to put 777 but it’s not that.
I tried to launch the script from another user (with root privileges) and get a warning to not launch bitwarden like that.
After a reboot of the VM, Bitwarden is starting automaticaly but I don’t see any container running from bitwarden user. My instance is accessible and working well.
