jcoffey-dev
c60028aad1
Two Dependabot PRs are stuck behind the same number. #35 raises the go directive to 1.26.0 in six modules, because golang.org/x/crypto v0.56.0 requires it -- x/crypto tracks the two most recent Go releases and 0.56 dropped 1.25. A module that says 1.26 cannot be built by the 1.25 this repository pins in two places, so that PR fails every Go job. #29 raises actions/setup-go to v7, which sets GOTOOLCHAIN=local. With that set, `go install golang.org/x/vuln/cmd/govulncheck@latest` cannot quietly fetch a newer toolchain, and stops with golang.org/x/[email protected] requires go >= 1.26.0 (running go 1.25.14) Under setup-go v5 the same install succeeded by downloading 1.26 behind our backs, which is its own reason to be on 1.26 deliberately instead. So: security-scan's go-version and all eight Dockerfiles move together, 1.25 -> 1.26. Nothing else needs to. A newer toolchain builds an older directive happily, so this stands on its own before #35 lands, and the go.mod files stay where they are here. Checked by building rather than by reading: the api and ingest images both build on golang:1.26-alpine, and api, ingest and enterprise still `go build ./...` clean against their existing 1.25 directives.
13 lines
538 B
Docker
13 lines
538 B
Docker
# Same shape as every other Go service's Dockerfile in this repo
|
|
# (alerting/Dockerfile, enterprise/Dockerfile) -- context is
|
|
# deploy/operator/ itself, no /proto dependency.
|
|
# docker build -f deploy/operator/Dockerfile -t cairnobs-tenant-operator deploy/operator/
|
|
FROM golang:1.26-alpine AS builder
|
|
WORKDIR /src
|
|
COPY . .
|
|
RUN CGO_ENABLED=0 GOOS=linux go build -o /out/tenant-operator ./cmd/tenant-operator
|
|
|
|
FROM gcr.io/distroless/static-debian12
|
|
COPY --from=builder /out/tenant-operator /tenant-operator
|
|
ENTRYPOINT ["/tenant-operator"]
|