MirrorHub/bitwarden_rs
0
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden synced 2024-11-13 21:41:43 +01:00
Code Issues Releases Wiki Activity

Showing how to bind host-port in the docker directive to a fixed IP and hence not expose it to all IPs on the network

muibusan 2019-08-10 14:32:34 +02:00
parent 5c7bdcf5e4
commit 9a76e52f09
1 changed files with 9 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
Starting-a-Container.md

@ -12,6 +12,13 @@ sudo podman run -d --name bitwarden -v /bw-data/:/data/:Z -p 80:8080 bitwardenrs
This will preserve any persistent data under `/bw-data/`, you can adapt the path to whatever suits you. This will preserve any persistent data under `/bw-data/`, you can adapt the path to whatever suits you.
The service will be exposed on port 80 or 8080. The service will be exposed on host-port 80 or 8080.
For non-x86 hardware or to run specific version, you can [[choose some other image|Which-Docker-image-to-use]]. For non-x86 hardware or to run specific version, you can [[choose some other image|Which-Docker-image-to-use]].
If your docker/bitwarden_rs runs on a device with a fixed IP, you can bind the host-port to that specific IP and hence prevent exposing the host-port to the whole world or network. Add the IP address (e.g. 192.168.0.2) in front of the host-port and container-port as follows:
```
# using Docker:
docker run -d --name bitwarden -v /bw-data/:/data/ -p 192.168.0.2:80:80 bitwardenrs/server:latest
```