atuin/Dockerfile

FROM lukemathwalker/cargo-chef:latest-rust-1.79.0-buster AS chef
WORKDIR app

FROM chef AS planner
COPY . .
RUN cargo chef prepare --recipe-path recipe.json

FROM chef AS builder

# Ensure working C compile setup (not installed by default in arm64 images)
RUN apt update && apt install build-essential -y

COPY --from=planner /app/recipe.json recipe.json
RUN cargo chef cook --release --recipe-path recipe.json

COPY . .
RUN cargo build --release --bin atuin

FROM debian:bullseye-20240722-slim AS runtime

RUN useradd -c 'atuin user' atuin && mkdir /config && chown atuin:atuin /config
# Install ca-certificates for webhooks to work
RUN apt update && apt install ca-certificates -y && rm -rf /var/lib/apt/lists/*
WORKDIR app

USER atuin

ENV TZ=Etc/UTC
ENV RUST_LOG=atuin::api=info
ENV ATUIN_CONFIG_DIR=/config

COPY --from=builder /app/target/release/atuin /usr/local/bin
ENTRYPOINT ["/usr/local/bin/atuin"]
chore(deps): bump lukemathwalker/cargo-chef (#2146) Bumps lukemathwalker/cargo-chef from latest-rust-1.78.0-buster to latest-rust-1.79.0-buster. --- updated-dependencies: - dependency-name: lukemathwalker/cargo-chef dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 2024-06-17 08:54:30 +02:00			`FROM lukemathwalker/cargo-chef:latest-rust-1.79.0-buster AS chef`
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00			`WORKDIR app`
fix: dockerfile with correct glibc (#198) * fix: dockerfile with correct glibc * chore: update server docs 2021-11-13 23:45:50 +01:00
			`FROM chef AS planner`
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00			`COPY . .`
fix: dockerfile with correct glibc (#198) * fix: dockerfile with correct glibc * chore: update server docs 2021-11-13 23:45:50 +01:00			`RUN cargo chef prepare --recipe-path recipe.json`
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00
fix: dockerfile with correct glibc (#198) * fix: dockerfile with correct glibc * chore: update server docs 2021-11-13 23:45:50 +01:00			`FROM chef AS builder`
Build ARM docker image in GitHub Actions using QEMU (#400) This PR updates the GH Action docker workflow to crossbuild the docker image for ARM using QEMU. This theoratically works but takes about for a clean build 2.5 hours, which may or may not be tolerable for each commit on `main`. A action run where the dependencies are already cached needs about 15 minutes with this PR. 2022-05-09 22:09:31 +02:00
			`# Ensure working C compile setup (not installed by default in arm64 images)`
chore(build): compile protobufs with protox (#2122) * chore(build): compile protobufs with protox protox is a pure-rust implementation of the protobuf compiler. Therefore, it can be managed by cargo. This removes the implicit dependency on protoc being available in the environment for the build. * fix(build): replace copypasta in build script The paths passed to `compile` aren't actually used by the build. `skip_protoc_run` prevents that. That's why a clean build succeeds even with this mistake. However, the paths are passed to a `cargo:rerun-if-changed` directive. So this mistake would've caused a failed incremental build if the protobuf definitions were changed. 2024-06-12 17:45:38 +02:00			`RUN apt update && apt install build-essential -y`
Build ARM docker image in GitHub Actions using QEMU (#400) This PR updates the GH Action docker workflow to crossbuild the docker image for ARM using QEMU. This theoratically works but takes about for a clean build 2.5 hours, which may or may not be tolerable for each commit on `main`. A action run where the dependencies are already cached needs about 15 minutes with this PR. 2022-05-09 22:09:31 +02:00
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00			`COPY --from=planner /app/recipe.json recipe.json`
			`RUN cargo chef cook --release --recipe-path recipe.json`

			`COPY . .`
			`RUN cargo build --release --bin atuin`

chore(deps): bump debian (#2320) Bumps debian from bullseye-20240701-slim to bullseye-20240722-slim. --- updated-dependencies: - dependency-name: debian dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 2024-07-30 17:47:24 +02:00			`FROM debian:bullseye-20240722-slim AS runtime`
Securize Dockerfile (#506) 2022-08-21 23:06:14 +02:00
			`RUN useradd -c 'atuin user' atuin && mkdir /config && chown atuin:atuin /config`
clean apt cache in Dockerfile (#932) * clean apt cache in Dockerfile * Change /app to app, to be in sync with changes from mainline 2023-06-16 22:59:52 +02:00			`# Install ca-certificates for webhooks to work`
			`RUN apt update && apt install ca-certificates -y && rm -rf /var/lib/apt/lists/*`
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00			`WORKDIR app`
Bugfixes, show time ago, perf improvements Also allow unique listing and more ergonomic cwd usage 2021-04-21 19:13:51 +02:00
Securize Dockerfile (#506) 2022-08-21 23:06:14 +02:00			`USER atuin`

Bugfixes, show time ago, perf improvements Also allow unique listing and more ergonomic cwd usage 2021-04-21 19:13:51 +02:00			`ENV TZ=Etc/UTC`
Update docs, unify on SQLx, bugfixes (#40) * Begin moving to sqlx for local too * Stupid scanners should just have a nice cup of tea Random internet shit searching for /.env or whatever * Remove diesel and rusqlite fully 2021-04-25 19:21:52 +02:00			`ENV RUST_LOG=atuin::api=info`
Bugfixes, show time ago, perf improvements Also allow unique listing and more ergonomic cwd usage 2021-04-21 19:13:51 +02:00			`ENV ATUIN_CONFIG_DIR=/config`

Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile 2021-04-20 22:53:07 +02:00			`COPY --from=builder /app/target/release/atuin /usr/local/bin`
			`ENTRYPOINT ["/usr/local/bin/atuin"]`