fix dockerfile
Unit Tests with docker compose and cargo / unit-test (push) Successful in 2m58s Details

This commit is contained in:
Alie 2024-11-29 16:49:59 +01:00
parent 0c2ee8a69b
commit 7fb94e17db
1 changed files with 5 additions and 30 deletions

View File

@ -1,48 +1,25 @@
# syntax=docker/dockerfile:1
# Comments are provided throughout this file to help you get started.
# If you need more help, visit the Dockerfile reference guide at
# https://docs.docker.com/engine/reference/builder/
################################################################################
# Create a stage for building the application.
ARG APP_NAME=mastodon-image-uploader-bot
FROM rust:1.79.0-slim-bullseye AS build
WORKDIR /app
ARG APP_NAME=mastodon-image-uploader-bot
RUN apt update && apt install pkg-config openssl libssl-dev -y
# Build the application.
# Leverage a cache mount to /usr/local/cargo/registry/
# for downloaded dependencies and a cache mount to /app/target/ for
# compiled dependencies which will speed up subsequent builds.
# Leverage a bind mount to the src directory to avoid having to copy the
# source code into the container. Once built, copy the executable to an
# output directory before the cache mounted /app/target is unmounted.
RUN --mount=type=bind,source=src,target=src \
--mount=type=bind,source=Cargo.toml,target=Cargo.toml \
--mount=type=bind,source=Cargo.lock,target=Cargo.lock \
<<EOF
set -e
cargo build --locked --release
ls ./target/release/$APP_NAME
cp ./target/release/$APP_NAME /bin/bot
EOF
################################################################################
# Create a new stage for running the application that contains the minimal
# runtime dependencies for the application. This often uses a different base
# image from the build stage where the necessary files are copied from the build
# stage.
#
# The example below uses the debian bullseye image as the foundation for running the app.
# By specifying the "bullseye-slim" tag, it will also use whatever happens to be the
# most recent version of that tag when you build your Dockerfile. If
# reproducability is important, consider using a digest
# (e.g., debian@sha256:ac707220fbd7b67fc19b112cee8170b41a9e97f703f588b2cdbbcdcecdd8af57).
FROM debian:bullseye-slim AS final
WORKDIR /app
RUN apt update && apt install pkg-config openssl libssl-dev curl -y
# Create a non-privileged user that the app will run under.
# See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user
ARG UID=10001
RUN adduser \
--disabled-password \
@ -52,8 +29,6 @@ RUN adduser \
botuser
USER botuser
# Copy the executable from the "build" stage.
COPY --from=build /bin/bot /bin/
# What the container should run when it is started.
CMD ["/bin/bot"]