0
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden synced 2024-12-16 10:33:43 +01:00
bitwarden_rs/docker/armv7/Dockerfile.alpine

138 lines
5 KiB
Text
Raw Normal View History

# syntax=docker/dockerfile:1
2020-09-22 00:39:39 +02:00
# This file was generated using a Jinja2 template.
# Please make your changes in `Dockerfile.j2` and then `make` the individual Dockerfiles.
2020-09-22 00:39:39 +02:00
# Using multistage build:
# https://docs.docker.com/develop/develop-images/multistage-build/
# https://whitfin.io/speeding-up-rust-docker-builds/
####################### VAULT BUILD IMAGE #######################
# The web-vault digest specifies a particular web-vault build on Docker Hub.
# Using the digest instead of the tag name provides better security,
# as the digest of an image is immutable, whereas a tag name can later
# be changed to point to a malicious image.
#
# To verify the current digest for a given tag name:
2021-04-27 23:18:32 +02:00
# - From https://hub.docker.com/r/vaultwarden/web-vault/tags,
# click the tag name to view the digest of the image it currently points to.
# - From the command line:
2022-06-04 19:07:02 +02:00
# $ docker pull vaultwarden/web-vault:v2022.05.0
# $ docker image inspect --format "{{.RepoDigests}}" vaultwarden/web-vault:v2022.05.0
# [vaultwarden/web-vault@sha256:7b07588398cf89488a1bfc7a5b75aa5877612674578bdedc098f1bc78555703f]
#
# - Conversely, to get the tag name from the digest:
2022-06-04 19:07:02 +02:00
# $ docker image inspect --format "{{.RepoTags}}" vaultwarden/web-vault@sha256:7b07588398cf89488a1bfc7a5b75aa5877612674578bdedc098f1bc78555703f
# [vaultwarden/web-vault:v2022.05.0]
2020-09-22 00:39:39 +02:00
#
2022-06-04 19:07:02 +02:00
FROM vaultwarden/web-vault@sha256:7b07588398cf89488a1bfc7a5b75aa5877612674578bdedc098f1bc78555703f as vault
2020-09-22 00:39:39 +02:00
########################## BUILD IMAGE ##########################
FROM blackdex/rust-musl:armv7-musleabihf-stable-1.61.0 as build
2020-09-22 00:39:39 +02:00
# Build time options to avoid dpkg warnings and help with reproducible builds.
ENV DEBIAN_FRONTEND=noninteractive \
LANG=C.UTF-8 \
TZ=UTC \
TERM=xterm-256color \
CARGO_HOME="/root/.cargo" \
USER="root"
2020-09-22 00:39:39 +02:00
# Create CARGO_HOME folder and don't download rust docs
RUN mkdir -pv "${CARGO_HOME}" \
&& rustup set profile minimal
2020-09-22 00:39:39 +02:00
# Creates a dummy project used to grab dependencies
RUN USER=root cargo new --bin /app
WORKDIR /app
# Copies over *only* your manifests and build files
COPY ./Cargo.* ./
COPY ./rust-toolchain ./rust-toolchain
COPY ./build.rs ./build.rs
RUN rustup target add armv7-unknown-linux-musleabihf
# Configure the DB ARG as late as possible to not invalidate the cached layers above
# Enable MiMalloc to improve performance on Alpine builds
ARG DB=sqlite,mysql,postgresql,enable_mimalloc
2020-09-22 00:39:39 +02:00
# Builds your dependencies and removes the
# dummy project, except the target folder
# This folder contains the compiled dependencies
RUN cargo build --features ${DB} --release --target=armv7-unknown-linux-musleabihf \
&& find . -not -path "./target*" -delete
2020-09-22 00:39:39 +02:00
# Copies the complete project
# To avoid copying unneeded files, use .dockerignore
COPY . .
# Make sure that we actually build the project
RUN touch src/main.rs
# Builds again, this time it'll just be
# your actual source files being built
# hadolint ignore=DL3059
2020-09-22 00:39:39 +02:00
RUN cargo build --features ${DB} --release --target=armv7-unknown-linux-musleabihf
# Create a special empty file which we check within the application.
# If this file exists, then we exit Vaultwarden to prevent data loss when someone forgets to use volumes.
# If you really really want to use volatile storage you can set the env `I_REALLY_WANT_VOLATILE_STORAGE=true`
# This file should disappear if a volume is mounted on-top of this using a docker volume.
# We run this in the build image and copy it over, because the runtime image could be missing some executables.
# hadolint ignore=DL3059
RUN touch /vaultwarden_docker_persistent_volume_check
2020-09-22 00:39:39 +02:00
######################## RUNTIME IMAGE ########################
# Create a new stage with a minimal image
# because we already have a binary built
FROM balenalib/armv7hf-alpine:3.15
ENV ROCKET_PROFILE="release" \
ROCKET_ADDRESS=0.0.0.0 \
ROCKET_PORT=80 \
SSL_CERT_DIR=/etc/ssl/certs
2020-09-22 00:39:39 +02:00
# hadolint ignore=DL3059
2020-09-22 00:39:39 +02:00
RUN [ "cross-build-start" ]
# Create data folder and Install needed libraries
RUN mkdir /data \
&& apk add --no-cache \
2020-09-22 00:39:39 +02:00
openssl \
tzdata \
2020-09-22 00:39:39 +02:00
curl \
dumb-init \
2020-09-22 00:39:39 +02:00
ca-certificates
# hadolint ignore=DL3059
2020-09-22 00:39:39 +02:00
RUN [ "cross-build-end" ]
VOLUME /data
EXPOSE 80
EXPOSE 3012
# Copies the files from the context (Rocket.toml file and web-vault)
# and the binary from the "build" stage to the current stage
WORKDIR /
2020-09-22 00:39:39 +02:00
COPY --from=vault /web-vault ./web-vault
COPY --from=build /vaultwarden_docker_persistent_volume_check /data/vaultwarden_docker_persistent_volume_check
2021-04-27 23:18:32 +02:00
COPY --from=build /app/target/armv7-unknown-linux-musleabihf/release/vaultwarden .
2020-09-22 00:39:39 +02:00
COPY docker/healthcheck.sh /healthcheck.sh
COPY docker/start.sh /start.sh
HEALTHCHECK --interval=60s --timeout=10s CMD ["/healthcheck.sh"]
# Configures the startup!
# We should be able to remove the dumb-init now with Rocket 0.5
# But the balenalib images have some issues with there entry.sh
# See: https://github.com/balena-io-library/base-images/issues/735
# Lets keep using dumb-init for now, since that is working fine.
ENTRYPOINT ["/usr/bin/dumb-init", "--"]
CMD ["/start.sh"]