vaultwarden
/
vaultwarden-alternativa-bitwarden
mirror of https://github.com/dani-garcia/vaultwarden.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Which container image to use (markdown)

Jeremy Lin 2021-03-18 15:20:09 -07:00
parent 9529ac30cf
commit ad3f9f5f95
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Which-container-image-to-use.md

@ -14,7 +14,7 @@ The `bitwardenrs/server` image has several tags, each of which represents some v
* `x.y.z` (e.g., `1.16.0`) -- Represents a specific released version. * `x.y.z` (e.g., `1.16.0`) -- Represents a specific released version.
* `alpine` -- Functionally the same as `latest`, but Alpine-based rather than Debian-based, resulting in a slimmer image. `latest` vs. `alpine` is mostly a matter of preference. However, note that the `alpine` tag currently supports only the `amd64` and `arm32v7` architectures, and only the SQLite and PostgreSQL database backends. * `alpine` -- With a few exceptions, this image is functionally the same as `latest`, but Alpine-based rather than Debian-based, resulting in a slimmer image. Therefore, `latest` vs. `alpine` is mostly a matter of preference. However, note that the `alpine` tag currently supports only the `amd64` and `arm32v7` architectures, and only the SQLite and PostgreSQL database backends.
* `x.y.z-alpine` (e.g., `1.16.0-alpine`) -- Similar to `alpine`, but represents a specific released version. * `x.y.z-alpine` (e.g., `1.16.0-alpine`) -- Similar to `alpine`, but represents a specific released version.