Robin Schneider
0d8d6858fc
The runtime image was not the last stage thus it was always build and left as untagged image. We can improve that. Refer to the docs for the `docker build --target` option: > Commands after the target stage will be skipped. Ref: https://docs.docker.com/engine/reference/commandline/build/#specifying-target-build-stage---target This commit simply moves the dpkg build stage patch above the runtime image stage.
30 lines
1.4 KiB
Diff
30 lines
1.4 KiB
Diff
--- git/docker/armv7/Dockerfile 2022-12-24 15:34:46.644360901 +0100
|
|
+++ Dockerfile 2022-12-24 18:15:38.065904150 +0100
|
|
@@ -104,6 +104,26 @@
|
|
# hadolint ignore=DL3059
|
|
RUN cargo build --features ${DB} --release --target=armv7-unknown-linux-gnueabihf
|
|
|
|
+####################### dpkg target ##########################
|
|
+FROM build as dpkg
|
|
+RUN mkdir /outdir
|
|
+RUN mkdir -p /vaultwarden_package/DEBIAN
|
|
+RUN mkdir -p /vaultwarden_package/usr/local/bin
|
|
+RUN mkdir -p /vaultwarden_package/usr/lib/systemd/system
|
|
+RUN mkdir -p /vaultwarden_package/etc/@@PACKAGEDIR@@
|
|
+RUN mkdir -p /vaultwarden_package/usr/share/@@PACKAGEDIR@@
|
|
+
|
|
+WORKDIR /vaultwarden_package
|
|
+COPY debian/control /vaultwarden_package/DEBIAN/control
|
|
+COPY debian/postinst /vaultwarden_package/DEBIAN/postinst
|
|
+COPY debian/conffiles /vaultwarden_package/DEBIAN/conffiles
|
|
+COPY debian/config.env /vaultwarden_package/etc/@@PACKAGEDIR@@
|
|
+COPY debian/@@EXECUTABLENAME@@.service /vaultwarden_package/usr/lib/systemd/system
|
|
+COPY --from=vault /web-vault /vaultwarden_package/usr/share/@@PACKAGEDIR@@/web-vault
|
|
+COPY --from=build app/target/armv7-unknown-linux-gnueabihf/release/vaultwarden /vaultwarden_package/usr/local/bin/@@EXECUTABLENAME@@
|
|
+
|
|
+RUN dpkg-deb --build . /outdir/@@PACKAGEDIR@@.deb
|
|
+
|
|
######################## RUNTIME IMAGE ########################
|
|
# Create a new stage with a minimal image
|
|
# because we already have a binary built
|