VictoriaMetrics/deployment/docker/builder/Dockerfile

ARG go_builder_image=non-existing
FROM $go_builder_image
STOPSIGNAL SIGINT
RUN apk add git gcc musl-dev make wget --no-cache && \
    mkdir /opt/cross-builder && \
    cd /opt/cross-builder && \
    for arch in aarch64 x86_64; do \
        wget \
            https://musl.cc/${arch}-linux-musl-cross.tgz \
            -O /opt/cross-builder/${arch}-musl.tgz \
            --no-verbose && \
        tar zxf ${arch}-musl.tgz -C ./  && \
        rm /opt/cross-builder/${arch}-musl.tgz; \
    done
all: suppress InvalidDefaultArgInFrom warning emitted by `docker build` when building Docker packages via `make package-` command Recent versions of `docker build` started generating the InvalidDefaultArgInFrom warning if Dockerfile contains an ARG without default value. While this warning doesn't affect building Docker packages via `make package-` commands, it is better suppressing the warning, so it doesn't clutter `make package-*` output with the noise, which can hide real issues in the future. 2024-09-03 14:00:25 +02:00			`ARG go_builder_image=non-existing`
deployment/docker: allow building docker images on top of any base image set via ROOT_IMAGE environment var For example, the following command will build VictoriaMetrics docker image on top of alpine image: ROOT_IMAGE=alpine make package-victoria-metrics 2020-04-20 00:09:52 +02:00			`FROM $go_builder_image`
Add SIGINT as stopsignal to docker file (#54) Add sigint as stopsignal to docker file. You can find more here: https://docs.docker.com/engine/reference/builder/#usage With this change, the main process inside the container will receive SIGINT, and after a grace period, SIGKILL. 2019-06-06 21:36:21 +02:00			`STOPSIGNAL SIGINT`
deployment/docker: upgrade Go builder for production builds from v1.17.7 to v1.18.0 See https://tip.golang.org/doc/go1.18 2022-03-16 13:07:40 +01:00			`RUN apk add git gcc musl-dev make wget --no-cache && \`
adds CGO build for arm64 (#2102) * adds CGO build for arm64 it must improve performance for arm64 based deployments of vmstorage and vmsingle for 15-20% it depends on gozstd package update for correct musl gozstd vendoring * typo fixes * docs/CHANGELOG.md: document the change Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com> 2022-02-08 15:25:59 +01:00			`mkdir /opt/cross-builder && \`
			`cd /opt/cross-builder && \`
deployment/docker: allow cross-platform building on arm64 platform (#6158) Added x86_64 libraries to allow building cross-platform images on arm64 2024-04-23 12:12:10 +02:00			`for arch in aarch64 x86_64; do \`
			`wget \`
			`https://musl.cc/${arch}-linux-musl-cross.tgz \`
			`-O /opt/cross-builder/${arch}-musl.tgz \`
			`--no-verbose && \`
			`tar zxf ${arch}-musl.tgz -C ./ && \`
			`rm /opt/cross-builder/${arch}-musl.tgz; \`
			`done`