github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-01 14:47:38 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/deployment/docker/Makefile

217 lines
7.9 KiB
Makefile
Raw Normal View History

deployment/docker/Makefile: mention that the Makefile rules must be invoked from the repository root
2019-12-11 21:32:45 +00:00
# All these commands must run from repository root.
deployment/docker: allow overriding docker namespace (#4265) It makes it easier for users who build and self-host images to publish their images without changing tags manually. Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com>
2023-05-08 06:34:05 +00:00
DOCKER_NAMESPACE ?= victoriametrics
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-19 22:09:52 +00:00
security: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1 See https://www.alpinelinux.org/posts/Alpine-3.20.1-released.html >including security fixes for: OPENSSL [CVE-2024-4741](https://security.alpinelinux.org/vuln/CVE-2024-4741) BUSYBOX [CVE-2023-42364](https://security.alpinelinux.org/vuln/CVE-2023-42364) [CVE-2023-42365](https://security.alpinelinux.org/vuln/CVE-2023-42365)
2024-07-09 09:38:05 +00:00
ROOT_IMAGE ?= alpine:3.20.1
deployment/docker: add scratch-based images (#6386) ### Describe Your Changes Scratch based images will be using a separate tag: "(version)-scratch" and will be built for the same architecture as regular images. This is useful for environments with higher security standards. In this case using alpine as base layer requires updating images more frequently in order to get the latest updates for the base image, even in case the user did not need to update VictoriaMetrics version. Tested that scratch images work for: - vmagent - enterprise with kafka and opensource - cluster - single-node No issues observed so far. cc: @tenmozes ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-06-03 09:43:28 +00:00
ROOT_IMAGE_SCRATCH ?= scratch
security: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1 See https://www.alpinelinux.org/posts/Alpine-3.20.1-released.html >including security fixes for: OPENSSL [CVE-2024-4741](https://security.alpinelinux.org/vuln/CVE-2024-4741) BUSYBOX [CVE-2023-42364](https://security.alpinelinux.org/vuln/CVE-2023-42364) [CVE-2023-42365](https://security.alpinelinux.org/vuln/CVE-2023-42365)
2024-07-09 09:38:05 +00:00
CERTS_IMAGE := alpine:3.20.1
deployment/docker/Makefile: use alpine 3.17.3 instead of alpine 3.18.0 for certs image, since alpine 3.18.0 doesnt work for cross-platform builds
2023-05-18 21:08:34 +00:00
deployment/docker: update Go builder from Go1.22.4 to Go1.22.5 See https://github.com/golang/go/issues?q=milestone%3AGo1.22.5+label%3ACherryPickApproved
2024-07-02 22:07:07 +00:00
GO_BUILDER_IMAGE := golang:1.22.5-alpine
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 14:25:59 +00:00
BUILDER_IMAGE := local/builder:2.0.0-$(shell echo $(GO_BUILDER_IMAGE) | tr :/ __)-1
all: run `apk update && apk upgrade` in base Alpine Docker image in order to get all the recent security fixes
2023-02-09 22:01:16 +00:00
BASE_IMAGE := local/base:1.1.4-$(shell echo $(ROOT_IMAGE) | tr :/ __)-$(shell echo $(CERTS_IMAGE) | tr :/ __)
Support building images via podman (#4978)
2023-11-09 08:50:21 +00:00
DOCKER ?= docker
DOCKER_RUN ?= $(DOCKER) run
DOCKER_BUILD ?= $(DOCKER) build
DOCKER_COMPOSE ?= $(DOCKER) compose
DOCKER_IMAGE_LS ?= $(DOCKER) image ls --format '{{.Repository}}:{{.Tag}}'
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
Rootless docker images by default (#358) * Rootless docker images by default * Migrate to rootless base image Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-03-27 19:18:32 +00:00
package-base:
Remove some repetitions in docker Makefile (#4764)
2023-08-02 11:04:38 +00:00
($(DOCKER_IMAGE_LS) | grep -q '$(BASE_IMAGE)$$') \
|| $(DOCKER_BUILD) \
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-19 22:09:52 +00:00
--build-arg root_image=$(ROOT_IMAGE) \
--build-arg certs_image=$(CERTS_IMAGE) \
deployment/docker: properly publish `latest` tag during `make publish-via-docker` This has been broken in f9902b3372f3a1b1ec86bed4f7679a34b8685cea
2021-02-16 15:42:24 +00:00
--tag $(BASE_IMAGE) \
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-19 22:09:52 +00:00
deployment/docker/base
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
package-builder:
Remove some repetitions in docker Makefile (#4764)
2023-08-02 11:04:38 +00:00
($(DOCKER_IMAGE_LS) | grep -q '$(BUILDER_IMAGE)$$') \
|| $(DOCKER_BUILD) \
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-19 22:09:52 +00:00
--build-arg go_builder_image=$(GO_BUILDER_IMAGE) \
deployment/docker: properly publish `latest` tag during `make publish-via-docker` This has been broken in f9902b3372f3a1b1ec86bed4f7679a34b8685cea
2021-02-16 15:42:24 +00:00
--tag $(BUILDER_IMAGE) \
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-19 22:09:52 +00:00
deployment/docker/builder
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
deployment/docker: use `docker buildx` for creating multiarch builds See https://github.com/docker/buildx/
2021-02-12 02:31:19 +00:00
app-via-docker: package-builder
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
mkdir -p gocache-for-docker
Support building images via podman (#4978)
2023-11-09 08:50:21 +00:00
$(DOCKER_RUN) --rm \
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
--user $(shell id -u):$(shell id -g) \
--mount type=bind,src="$(shell pwd)",dst=/VictoriaMetrics \
-w /VictoriaMetrics \
--mount type=bind,src="$(shell pwd)/gocache-for-docker",dst=/gocache \
--env GOCACHE=/gocache \
all: small updates after PR #114
2019-07-23 16:54:50 +00:00
$(DOCKER_OPTS) \
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
$(BUILDER_IMAGE) \
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 17:39:05 +00:00
go build $(RACE) -trimpath -buildvcs=false \
keep debug symbols (#438) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-05-19 22:21:46 +00:00
-ldflags "-extldflags '-static' $(GO_BUILDINFO)" \
moves prod images build into alpine container with musl (#1640) adds gcc and musl-dev to builder container
2021-09-23 21:14:11 +00:00
-tags 'netgo osusergo nethttpomithttp2 musl' \
deployment/docker: remove file system paths from the compiled binary
2019-09-13 19:43:56 +00:00
-o bin/$(APP_NAME)$(APP_SUFFIX)-prod $(PKG_PREFIX)/app/$(APP_NAME)
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 18:49:07 +00:00
app-via-docker-windows: package-builder
mkdir -p gocache-for-docker
Support building images via podman (#4978)
2023-11-09 08:50:21 +00:00
$(DOCKER_RUN) --rm \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 18:49:07 +00:00
--user $(shell id -u):$(shell id -g) \
--mount type=bind,src="$(shell pwd)",dst=/VictoriaMetrics \
-w /VictoriaMetrics \
--mount type=bind,src="$(shell pwd)/gocache-for-docker",dst=/gocache \
--env GOCACHE=/gocache \
$(DOCKER_OPTS) \
$(BUILDER_IMAGE) \
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 17:39:05 +00:00
go build $(RACE) -trimpath -buildvcs=false \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 18:49:07 +00:00
-ldflags "-s -w -extldflags '-static' $(GO_BUILDINFO)" \
-tags 'netgo osusergo nethttpomithttp2' \
-o bin/$(APP_NAME)-windows$(APP_SUFFIX)-prod.exe $(PKG_PREFIX)/app/$(APP_NAME)
deployment/docker: use `docker buildx` for creating multiarch builds See https://github.com/docker/buildx/
2021-02-12 02:31:19 +00:00
package-via-docker: package-base
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
($(DOCKER_IMAGE_LS) | grep -q '$(DOCKER_NAMESPACE)/$(APP_NAME):$(PKG_TAG)$(APP_SUFFIX)$(RACE)$$') || (\
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
$(MAKE) app-via-docker && \
Remove some repetitions in docker Makefile (#4764)
2023-08-02 11:04:38 +00:00
$(DOCKER_BUILD) \
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
--build-arg src_binary=$(APP_NAME)$(APP_SUFFIX)-prod \
Rootless docker images by default (#358) * Rootless docker images by default * Migrate to rootless base image Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-03-27 19:18:32 +00:00
--build-arg base_image=$(BASE_IMAGE) \
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
--tag $(DOCKER_NAMESPACE)/$(APP_NAME):$(PKG_TAG)$(APP_SUFFIX)$(RACE) \
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
-f app/$(APP_NAME)/deployment/Dockerfile bin)
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 20:51:33 +00:00
publish-via-docker:
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
$(MAKE_PARALLEL) app-via-docker-linux-amd64 \
app-via-docker-linux-arm \
app-via-docker-linux-arm64 \
app-via-docker-linux-ppc64le \
app-via-docker-linux-386
Support building images via podman (#4978)
2023-11-09 08:50:21 +00:00
$(DOCKER) buildx build \
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
--platform=linux/amd64,linux/arm,linux/arm64,linux/ppc64le,linux/386 \
deployment/docker: use `docker buildx` for creating multiarch builds See https://github.com/docker/buildx/
2021-02-12 02:31:19 +00:00
--build-arg certs_image=$(CERTS_IMAGE) \
--build-arg root_image=$(ROOT_IMAGE) \
--build-arg APP_NAME=$(APP_NAME) \
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
--tag $(DOCKER_NAMESPACE)/$(APP_NAME):$(PKG_TAG)$(RACE) \
--tag $(DOCKER_NAMESPACE)/$(APP_NAME):$(LATEST_TAG)$(RACE) \
deployment/docker: use `docker buildx` for creating multiarch builds See https://github.com/docker/buildx/
2021-02-12 02:31:19 +00:00
-o type=image \
deployment/docker: disable provenance in buildx (#4911) * deployment/docker: disable provenance in buildx it must fix an issue with multi-platform manifest generation at buildx >= 0.10 backward compatibility was broken and generated image cannot be used with docker systems that doesn't support oci. disabling attestat temporary fixes it. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4907 https://docs.docker.com/build/attestations/slsa-provenance/ * Update docs/CHANGELOG.md --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2023-08-29 14:29:14 +00:00
--provenance=false \
deployment/docker: use `docker buildx` for creating multiarch builds See https://github.com/docker/buildx/
2021-02-12 02:31:19 +00:00
-f app/$(APP_NAME)/multiarch/Dockerfile \
--push \
bin
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
$(DOCKER) buildx build \
--platform=linux/amd64,linux/arm,linux/arm64,linux/ppc64le,linux/386 \
--build-arg certs_image=$(CERTS_IMAGE) \
--build-arg root_image=$(ROOT_IMAGE_SCRATCH) \
--build-arg APP_NAME=$(APP_NAME) \
--tag $(DOCKER_NAMESPACE)/$(APP_NAME):$(PKG_TAG)$(RACE)-scratch \
--tag $(DOCKER_NAMESPACE)/$(APP_NAME):$(LATEST_TAG)$(RACE)-scratch \
-o type=image \
--provenance=false \
-f app/$(APP_NAME)/multiarch/Dockerfile \
--push \
bin
cd bin && rm -rf \
$(APP_NAME)-linux-amd64-prod \
$(APP_NAME)-linux-arm-prod \
$(APP_NAME)-linux-arm64-prod \
$(APP_NAME)-linux-ppc64le-prod \
$(APP_NAME)-linux-386-prod
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
run-via-docker: package-via-docker
Support building images via podman (#4978)
2023-11-09 08:50:21 +00:00
$(DOCKER_RUN) -it --rm \
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
--user $(shell id -u):$(shell id -g) \
--net host \
$(DOCKER_OPTS) \
Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" This reverts commit 6b128da811634af721b15b06d6f07a1e91cd4297. Reason for revert: this complicates and slows down CI/CD without giving significant benefits in return. The idea of automatic building, publishing and deploying Docker images to our playground on every pull request and commit isn't very bright because of the following reasons: - It slows down CI/CD pipeline - It increases costs on CPU time spent at CI/CD pipeline - It contradicts goal #7 at https://docs.victoriametrics.com/goals/#goals and non-goal #8 at https://docs.victoriametrics.com/goals/#non-goals The previous workflow was much better - if we need to deploy some new Docker image at playground or staging environment, then just __manually__ build and deploy the needed Docker image there. If the manual process requires making too many steps, then think on how to automate these steps into a single Makefile command. Updates https://github.com/VictoriaMetrics/ops/pull/1297 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6515
2024-07-16 11:27:06 +00:00
$(DOCKER_NAMESPACE)/$(APP_NAME):$(PKG_TAG)$(APP_SUFFIX)$(RACE) $(ARGS)
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-goos-goarch:
APP_SUFFIX='-$(GOOS)-$(GOARCH)' \
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
DOCKER_OPTS='--env CGO_ENABLED=$(CGO_ENABLED) --env GOOS=$(GOOS) --env GOARCH=$(GOARCH) $(foreach v,$(EXTRA_DOCKER_ENVS),--env $(v))' \
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
$(MAKE) app-via-docker
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-pure:
APP_SUFFIX='-pure' DOCKER_OPTS='--env CGO_ENABLED=0' $(MAKE) app-via-docker
adds release build for macos darwin amd64 and arm64 (#2185) * adds release build for macos darwin amd64 and arm64 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1896 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1851 * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-14 15:28:56 +00:00
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 12:42:48 +00:00
app-via-docker-linux-amd64:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
EXTRA_DOCKER_ENVS='CC=/opt/cross-builder/x86_64-linux-musl-cross/bin/x86_64-linux-musl-gcc' \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
CGO_ENABLED=1 GOOS=linux GOARCH=amd64 $(MAKE) app-via-docker-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 12:42:48 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-linux-arm64:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
EXTRA_DOCKER_ENVS='CC=/opt/cross-builder/aarch64-linux-musl-cross/bin/aarch64-linux-musl-gcc' \
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 10:12:10 +00:00
CGO_ENABLED=1 GOOS=linux GOARCH=arm64 $(MAKE) app-via-docker-goos-goarch
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 14:25:59 +00:00
deployment/docker/Makefile: group app-via-docker-* and package-via-docker-* rules with CGO_ENABLED=1 together for better maintainability
2024-05-12 21:09:55 +00:00
app-via-docker-linux-arm:
EXTRA_DOCKER_ENVS='GOARM=5' \
CGO_ENABLED=0 GOOS=linux GOARCH=arm $(MAKE) app-via-docker-goos-goarch
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-linux-ppc64le:
CGO_ENABLED=0 GOOS=linux GOARCH=ppc64le $(MAKE) app-via-docker-goos-goarch
all: use gozstd instead of pure Go zstd for GOARCH=amd64
2019-12-24 10:42:42 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-linux-386:
CGO_ENABLED=0 GOOS=linux GOARCH=386 $(MAKE) app-via-docker-goos-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-darwin-amd64:
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 $(MAKE) app-via-docker-goos-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-darwin-arm64:
CGO_ENABLED=0 GOOS=darwin GOARCH=arm64 $(MAKE) app-via-docker-goos-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-freebsd-amd64:
CGO_ENABLED=0 GOOS=freebsd GOARCH=amd64 $(MAKE) app-via-docker-goos-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
app-via-docker-openbsd-amd64:
CGO_ENABLED=0 GOOS=openbsd GOARCH=amd64 $(MAKE) app-via-docker-goos-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 18:49:07 +00:00
app-via-docker-windows-amd64:
deployment/docker/Makefile: properly add amd64 suffix to windows binary names
2023-03-19 06:29:44 +00:00
APP_SUFFIX='-amd64' \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
DOCKER_OPTS='--env CGO_ENABLED=0 --env GOOS=windows --env GOARCH=amd64' \
$(MAKE) app-via-docker-windows
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 18:49:07 +00:00
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
package-via-docker-goarch:
APP_SUFFIX='-$(GOARCH)' \
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
DOCKER_OPTS='--env CGO_ENABLED=$(CGO_ENABLED) --env GOOS=linux --env GOARCH=$(GOARCH) $(foreach v,$(EXTRA_DOCKER_ENVS),--env $(v))' \
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
$(MAKE) package-via-docker
package-via-docker-pure:
APP_SUFFIX='-pure' DOCKER_OPTS='--env CGO_ENABLED=0' $(MAKE) package-via-docker
package-via-docker-amd64:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
EXTRA_DOCKER_ENVS='CC=/opt/cross-builder/x86_64-linux-musl-cross/bin/x86_64-linux-musl-gcc' \
deployment: fix typo after https://github.com/VictoriaMetrics/VictoriaMetrics/commit/cb19335a9faf33865b71fac792254b8169005291 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-07-05 09:02:01 +00:00
CGO_ENABLED=1 GOARCH=amd64 $(MAKE) package-via-docker-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
package-via-docker-arm64:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
EXTRA_DOCKER_ENVS='CC=/opt/cross-builder/aarch64-linux-musl-cross/bin/aarch64-linux-musl-gcc' \
deployment: update makefile package-* targets (#6172) Updated package targets in a same manner, how it's done for publish ones in https://github.com/VictoriaMetrics/VictoriaMetrics/commit/7958f3886467aef1a386e3111136f1d3c59f7149
2024-04-24 16:29:32 +00:00
CGO_ENABLED=1 GOARCH=arm64 $(MAKE) package-via-docker-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
deployment/docker/Makefile: group app-via-docker-* and package-via-docker-* rules with CGO_ENABLED=1 together for better maintainability
2024-05-12 21:09:55 +00:00
package-via-docker-arm:
EXTRA_DOCKER_ENVS='GOARM=5' \
CGO_ENABLED=0 GOARCH=arm $(MAKE) package-via-docker-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
package-via-docker-ppc64le:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
CGO_ENABLED=0 GOARCH=ppc64le $(MAKE) package-via-docker-goarch
all: publish Docker images for the following GOARCH: amd64, arm, arm64, ppc64le and 386 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/258
2019-12-11 21:06:53 +00:00
package-via-docker-386:
deployment/docker/Makefile: rename EXTRA_ENVS to EXTRA_DOCKER_ENVS The purpose of EXTRA_DOCKER_ENVS name is more clear than EXTRA_ENVS. While at it, make the following small fixes: - Pass GOARM=5 to Docker builder when building Docker packages for GOARCH=arm in the same way it is passed to the builder when building production binaries for GOARCH=arm. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4965 - Set GCO_ENABLED=1 for package-via-docker-amd64, which has been accidentally removed in 07496d7d922ed36e6f71e41ff129bfa48d8812b4 - Consistently use 'CGO_ENABLED=... GOARCH=...' order of env vars at package-via-docker-*, because this order is used in app-via-docker-* Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6158 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6172 This is a follow-up for 07496d7d922ed36e6f71e41ff129bfa48d8812b4 and 7958f3886467aef1a386e3111136f1d3c59f7149
2024-05-12 20:23:28 +00:00
CGO_ENABLED=0 GOARCH=386 $(MAKE) package-via-docker-goarch
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
remove-docker-images:
Remove some repetitions in docker Makefile (#4764)
2023-08-02 11:04:38 +00:00
docker image ls --format '{{.ID}}' | xargs docker image rm -f
deployment/docker: move cluster compose env to master branch (#3130) * deployment/docker: move cluster compose env to master branch The change supposed to simplify the process of maintaining for single/cluster docker-compose envs, alerts, dashboards. It also supposes to reduce confusion for users when looking for cluster related alerts/configs. Signed-off-by: hagen1778 <roman@victoriametrics.com> * deployment/docker: move cluster compose env to master branch Review updates. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-21 08:48:38 +00:00
docker-single-up:
deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2 (#4314) deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2
2023-05-17 11:14:24 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose.yml up -d
deployment/docker: move cluster compose env to master branch (#3130) * deployment/docker: move cluster compose env to master branch The change supposed to simplify the process of maintaining for single/cluster docker-compose envs, alerts, dashboards. It also supposes to reduce confusion for users when looking for cluster related alerts/configs. Signed-off-by: hagen1778 <roman@victoriametrics.com> * deployment/docker: move cluster compose env to master branch Review updates. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-21 08:48:38 +00:00
docker-single-down:
deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2 (#4314) deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2
2023-05-17 11:14:24 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose.yml down -v
deployment/docker: move cluster compose env to master branch (#3130) * deployment/docker: move cluster compose env to master branch The change supposed to simplify the process of maintaining for single/cluster docker-compose envs, alerts, dashboards. It also supposes to reduce confusion for users when looking for cluster related alerts/configs. Signed-off-by: hagen1778 <roman@victoriametrics.com> * deployment/docker: move cluster compose env to master branch Review updates. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-21 08:48:38 +00:00
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 14:45:31 +00:00
docker-single-vm-datasource-up:
deployment/docker: follow-up https://github.com/VictoriaMetrics/VictoriaMetrics/commit/38b2a5bc44dab2892c3481e3ea46869a824da18c * Simplify folder structure * mention datasource in README Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-22 15:05:44 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose.yml -f deployment/docker/vm-datasource/docker-compose.yml up -d
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 14:45:31 +00:00
docker-single-vm-datasource-down:
deployment/docker: follow-up https://github.com/VictoriaMetrics/VictoriaMetrics/commit/38b2a5bc44dab2892c3481e3ea46869a824da18c * Simplify folder structure * mention datasource in README Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-22 15:05:44 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose.yml -f deployment/docker/vm-datasource/docker-compose.yml down -v
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 14:45:31 +00:00
deployment/docker: move cluster compose env to master branch (#3130) * deployment/docker: move cluster compose env to master branch The change supposed to simplify the process of maintaining for single/cluster docker-compose envs, alerts, dashboards. It also supposes to reduce confusion for users when looking for cluster related alerts/configs. Signed-off-by: hagen1778 <roman@victoriametrics.com> * deployment/docker: move cluster compose env to master branch Review updates. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-21 08:48:38 +00:00
docker-cluster-up:
deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2 (#4314) deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2
2023-05-17 11:14:24 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-cluster.yml up -d
deployment/docker: move cluster compose env to master branch (#3130) * deployment/docker: move cluster compose env to master branch The change supposed to simplify the process of maintaining for single/cluster docker-compose envs, alerts, dashboards. It also supposes to reduce confusion for users when looking for cluster related alerts/configs. Signed-off-by: hagen1778 <roman@victoriametrics.com> * deployment/docker: move cluster compose env to master branch Review updates. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-21 08:48:38 +00:00
docker-cluster-down:
deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2 (#4314) deployment/docker/Makefile: updated docker compose commands regarding migration from V1 to V2
2023-05-17 11:14:24 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-cluster.yml down -v
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 14:45:31 +00:00
docker-cluster-vm-datasource-up:
deployment/docker: follow-up https://github.com/VictoriaMetrics/VictoriaMetrics/commit/38b2a5bc44dab2892c3481e3ea46869a824da18c * Simplify folder structure * mention datasource in README Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-22 15:05:44 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-cluster.yml -f deployment/docker/vm-datasource/docker-compose-cluster.yml up -d
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 14:45:31 +00:00
docker-cluster-vm-datasource-down:
deployment/docker: follow-up https://github.com/VictoriaMetrics/VictoriaMetrics/commit/38b2a5bc44dab2892c3481e3ea46869a824da18c * Simplify folder structure * mention datasource in README Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-22 15:05:44 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-cluster.yml -f deployment/docker/vm-datasource/docker-compose-cluster.yml down -v
deployment: create a separate env for VictoriaLogs (#5857) * deployment: create a separate env for VictoriaLogs The new environment consists of the following components: * VictoriaLogs * fluentbit for collecting logs and sending to VictoriaLogs * VictoriaMetrics for scraping and storing metrics from fluentbit and VictoriaLogs * Grafana with VictoriaLogs datasource for monitoring ----------------- The motivation for creating a separate environment is to simplify existing environments and make it easier to update or modify them in future. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-26 09:33:04 +00:00
docker-victorialogs-up:
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-victorialogs.yml up -d
docker-victorialogs-down:
deployment/docker: update Go builder from Go1.21.7 to Go1.22.1 See https://github.com/golang/go/issues?q=milestone%3AGo1.22.1+label%3ACherryPickApproved
2024-03-06 19:04:09 +00:00
$(DOCKER_COMPOSE) -f deployment/docker/docker-compose-victorialogs.yml down -v
Reference in a new issue Copy permalink