From 3b620d1a500594a15d21d8c79709eaa117823a03 Mon Sep 17 00:00:00 2001 From: Eric Date: Fri, 2 Aug 2019 13:25:36 +0200 Subject: [PATCH] Updated info about Podman --- Updating-the-bitwarden-image.md | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/Updating-the-bitwarden-image.md b/Updating-the-bitwarden-image.md index d29055d..eaf13ef 100644 --- a/Updating-the-bitwarden-image.md +++ b/Updating-the-bitwarden-image.md @@ -35,12 +35,31 @@ docker rm bitwarden_data # Alternatively you can keep data container around for future updates in which case you can skip last step. ``` +bitwarden_rs can also be run with Podman, which is an open source Docker alternative. + +```sh +# Pull the latest version +podman pull bitwardenrs/server:latest + +# Stop and remove the old container +podman stop bitwarden +podman rm bitwarden + +# Start new container with the data mounted +podman run -d --name bitwarden -v /bw-data/:/data/:Z -p 8080:8080 bitwardenrs/server:latest +``` +Then visit [http://localhost:8080](http://localhost:8080). It is then recommended to use a reverse proxy to be able to use port `:80`. + +If you want to run the container as root, do this instead: +```sh +podman run -d --name bitwarden -v /bw-data/:/data/:Z -p 80:8080 bitwardenrs/server:latest +``` ## Updating when using systemd service (in this case Debian/Rasbian) ```sh -Sudo systemctl restart bitwarden.service -Sudo docker prune -f +sudo systemctl restart bitwarden.service +sudo docker prune -f #WARNING this could delete stopped or unused containers, etc. not associated with bitwarden_rs #be carefull and look which containers you need docker ps -a