Files
archie/Dockerfile.archied
T
sam 54be74ae89 feat(releaseupdate): stamp install type at build time, fail closed on unknown
/update could report success at the correct target version while the
archie-agent container running it never actually changed: the update
mechanism trusted the configured installer's exit code and reported
whatever version number the release claimed, with nothing verifying
the two agreed.

The first piece of the fix: a new internal/installtype package
reports how a binary was built for distribution (Type(), defaulting
to "unknown"), stamped once per release artifact via
"-ldflags -X .../installtype.buildType=<value>" rather than guessed
at runtime by probing the environment -- restic and Tailscale both
treat "which install shape is this" as a build-time decision for the
same reason: a probed signal is guessable, a compiled-in one is not.

releaseupdate.Service.Install now refuses to run the configured
Installer at all when InstallType is unset or installtype.Unknown, so
an unstamped or misconfigured build can no longer silently attempt an
update it has no way to know is even the right kind for how this
instance was deployed. Wired through every real archied build path so
the gate doesn't just exist in principle: Taskfile.yml's build task
(binary), Dockerfile.archied (container), and install.sh (binary) all
now stamp it; cmd/archied/telegram_setup.go wires
Service.InstallType from installtype.Type().

Configuration-page display of install type/version and post-update
verification against the actually-running reference (not just the
installer's reported version) remain open -- this lands the
correctness gate, not the full observability surface.

Refs #522
2026-08-15 10:34:46 +10:00

39 lines
1.8 KiB
Docker

# archied — the archie daemon, built as a standalone container.
# Run via docker compose alongside NATS.
FROM golang:1.26-trixie AS builder
WORKDIR /src
COPY go.mod go.sum ./
RUN go mod download
COPY . .
ARG GATEWAY_VERSION=dev
ARG RUNTIME_VERSION=dev
RUN CGO_ENABLED=0 go build \
-ldflags "-X main.gatewayVersion=${GATEWAY_VERSION} -X main.runtimeVersion=${RUNTIME_VERSION} -X github.com/samcharles93/archie-core/internal/installtype.buildType=container" \
-o /usr/local/bin/archied ./cmd/archied/
# archied is static, but this can't be scratch: in inprocess mode the daemon
# runs agent tools itself, and the shell tool invokes bash; codesearch shells
# to git. Worktrees don't count — internal/worktree uses go-git. This image
# is not part of the current deployment (docker-compose.yml only builds
# Dockerfile, the agent image; archied runs on the host under systemd), but
# if it's ever used in inprocess mode, grep needs ripgrep on PATH -- it is
# no longer embedded in the binary.
#
# No Node: the builtin tools (read/write/edit/find/grep/shell/test) cover what
# desktop-commander did. Any npx-launched MCP stdio server will now fail to
# start, and a failed provider rolls back the tool-provider family and exits
# the daemon — so remove tools.mcp_servers entries needing npx before
# deploying this image.
FROM debian:trixie-slim
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates git && \
rm -rf /var/lib/apt/lists/*
COPY --from=builder /usr/local/bin/archied /usr/local/bin/archied
ARG GATEWAY_VERSION=dev
ARG RUNTIME_VERSION=dev
LABEL org.opencontainers.image.version="${GATEWAY_VERSION}"
LABEL cloud.catlow.archie.runtime-version="${RUNTIME_VERSION}"
COPY CHANGELOG.archied.md /usr/share/archie/CHANGELOG.archied.md
COPY CHANGELOG.archie.md /usr/share/archie/CHANGELOG.archie.md
ENTRYPOINT ["archied"]