f097c0f4d5
Some checks failed
CI/CD / lint (pull_request) Successful in 1m20s
CI/CD / test (pull_request) Successful in 1m30s
CI/CD / typecheck (pull_request) Successful in 2m52s
CI/CD / smoke (pull_request) Failing after 2m1s
CI/CD / build (pull_request) Successful in 2m23s
CI/CD / publish (pull_request) Has been skipped
Upstream docker.gitea.com/gitea-mcp-server is distroless — `Cmd` is ["/app/gitea-mcp"] and there is no /bin/sh at any path (verified by exec'ing every candidate against the running pod). That is fine until the server wants secretDelivery: injector. The OpenBao agent renders secrets to a FILE, so mcpd wraps the container command as `sh -c '. /vault/secrets/<name>; exec "$0" "$@"'`, which needs a shell. gitea was the only server in the fleet blocked on this, and so the only one whose token had to stay inline in its pod spec. Copying one static Go binary onto debian:stable-slim is cheaper than building and maintaining a static envexec shim, and follows the precedent in deploy/Dockerfile.docmost-mcp — this repo already rebuilds third-party MCP servers when it needs to change how they run. ca-certificates is required rather than incidental: the binary talks HTTPS to mysources.co.uk and the distroless base shipped a trust store we are leaving behind. Verified in the built image: shell present, binary runs, ca-certificates.crt present. ENTRYPOINT is kept so the plain (non-injected) path behaves exactly like upstream; mcpd replaces it with the sourcing wrapper only when the server opts in. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018vybEitX4FykeMatKe5Xki
37 lines
1.6 KiB
Docker
37 lines
1.6 KiB
Docker
# gitea-mcp-server, rebuilt on a shell-bearing base.
|
|
#
|
|
# WHY THIS EXISTS
|
|
# ---------------
|
|
# Upstream `docker.gitea.com/gitea-mcp-server` is distroless: `Cmd` is
|
|
# ["/app/gitea-mcp"] and there is no /bin/sh at any path (verified by exec'ing
|
|
# every candidate against the running pod).
|
|
#
|
|
# That is fine until the server needs `secretDelivery: injector`. The OpenBao
|
|
# agent renders secrets to a FILE, so mcpd wraps the container command as
|
|
# `sh -c '. /vault/secrets/<name>; exec "$0" "$@"'` — which needs a shell. With
|
|
# no shell the pod cannot source its own credentials, and gitea was the single
|
|
# server in the fleet blocked on this.
|
|
#
|
|
# Copying one static Go binary onto debian:stable-slim is cheaper than building
|
|
# and maintaining a static "envexec" shim, and follows the precedent already set
|
|
# by deploy/Dockerfile.docmost-mcp — this repo already rebuilds third-party MCP
|
|
# servers when it needs to change how they run.
|
|
#
|
|
# ca-certificates is required, not incidental: the binary talks HTTPS to
|
|
# https://mysources.co.uk and a distroless base ships its own trust store which
|
|
# we are leaving behind.
|
|
FROM debian:stable-slim
|
|
|
|
RUN apt-get update \
|
|
&& apt-get install -y --no-install-recommends ca-certificates \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
COPY --from=docker.gitea.com/gitea-mcp-server:latest /app/gitea-mcp /usr/local/bin/gitea-mcp
|
|
|
|
WORKDIR /app
|
|
|
|
# Kept as ENTRYPOINT so the plain (non-injected) path behaves exactly like
|
|
# upstream. mcpd REPLACES this with the sourcing wrapper when the server opts
|
|
# into injected delivery — that is why a shell has to exist in the image.
|
|
ENTRYPOINT ["/usr/local/bin/gitea-mcp"]
|