rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-25 11:19:21 -07:00
Code Issues Packages Projects Releases Wiki Activity

Updated Starting a Container (markdown)

My1
2019-10-11 11:15:37 +02:00
parent 5b573ea0d2
commit 5bded6e988
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Starting-a-Container.md

@@ -1,3 +1,7 @@
Note that the `docker run` command has a slightly misleading name, as it rather creates a container, rather than just starting it, leading to conflicts when using `docker run` after just stopping the container without removing it. For a plain start, see below.
# Creating the Container
The persistent data is stored under /data inside the container, so the only requirement for persistent deployment using Docker is to mount persistent volume at the path: The persistent data is stored under /data inside the container, so the only requirement for persistent deployment using Docker is to mount persistent volume at the path:
```sh ```sh
@@ -22,3 +26,10 @@ If your docker/bitwarden_rs runs on a device with a fixed IP, you can bind the h
# using Docker: # using Docker:
docker run -d --name bitwarden -v /bw-data/:/data/ -p 192.168.0.2:80:80 bitwardenrs/server:latest docker run -d --name bitwarden -v /bw-data/:/data/ -p 192.168.0.2:80:80 bitwardenrs/server:latest
``` ```
# Starting the container
If the container has been stopped by `docker stop bitwarden`, a reboot or any other reason you can just start it up again by using
```
docker start bitwarden
```