![]() If you say for instance -p 9345:7777, it means that the port 9345 on the host will be directly connected with port 7777 on the container. This is the -p option, one that maps the container port to the host network. Minor edit: with and without quotes around 1000:1000 yields that same issue, I’ve added quotes because IIRC yml does some funky interpretation for octal numbers or some such and strings are safe. This is why docker provides the ability to expose this container port to the server. If I comment out user: "1000:1000" then the container launches fine. to Vaultwarden as BYOPM hosts a Bitwarden instance and the Docker Image of Bitwarden. I’ve since started with a scratch contianer and nuking between config changes via:ĭocker container stop testing_bitwarden_1 & echo 'y' | docker container prune & docker-compose up bitwarden This article is using Vaultwarden, not the Bitwarden server. When that didn’t work I tried with a different user/group 1001:1001. I originally had a data volume I tried using chown to change ownership to the 1000:1000 user:group. ![]() thread 'main' panicked at 'Can't connect to DB: BadConnection("Unable to open the database file")': src/main.rs:229 The default config works without issue, but the second I try to assign user/group the container seizes with: ![]() I spun up a docker container the other day, worked out reverse proxying w/ tls, my backup solution, and now trying to do some basic hardening. SIGNUPS_ALLOWED: 'true' # set to false to disable signups WEBSOCKET_ENABLED: 'true' # Required to use websockets
0 Comments
Leave a Reply. |