mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2025-01-10 15:14:09 +00:00
deployment/docker: update Go builder from Go1.21.5 to Go1.21.6
This commit is contained in:
parent
b546c31589
commit
992d239745
3 changed files with 4 additions and 2 deletions
|
@ -1,4 +1,4 @@
|
|||
FROM golang:1.21.5 as build-web-stage
|
||||
FROM golang:1.21.6 as build-web-stage
|
||||
COPY build /build
|
||||
|
||||
WORKDIR /build
|
||||
|
|
|
@ -5,7 +5,7 @@ DOCKER_NAMESPACE ?= victoriametrics
|
|||
ROOT_IMAGE ?= alpine:3.19.0
|
||||
CERTS_IMAGE := alpine:3.19.0
|
||||
|
||||
GO_BUILDER_IMAGE := golang:1.21.5-alpine
|
||||
GO_BUILDER_IMAGE := golang:1.21.6-alpine
|
||||
BUILDER_IMAGE := local/builder:2.0.0-$(shell echo $(GO_BUILDER_IMAGE) | tr :/ __)-1
|
||||
BASE_IMAGE := local/base:1.1.4-$(shell echo $(ROOT_IMAGE) | tr :/ __)-$(shell echo $(CERTS_IMAGE) | tr :/ __)
|
||||
DOCKER_BUILD ?= docker build
|
||||
|
|
|
@ -11,6 +11,8 @@ The following `tip` changes can be tested by building VictoriaMetrics components
|
|||
|
||||
## v1.93.x long-time support release (LTS)
|
||||
|
||||
* SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See [the list of issues addressed in Go1.21.6](https://github.com/golang/go/issues?q=milestone%3AGo1.21.6+label%3ACherryPickApproved).
|
||||
|
||||
* BUGFIX: `vminsert`: properly accept samples via [OpenTelemetry data ingestion protocol](https://docs.victoriametrics.com/#sending-data-via-opentelemetry) when these samples have no [resource attributes](https://opentelemetry.io/docs/instrumentation/go/resources/). Previously such samples were silently skipped.
|
||||
* BUGFIX: `vmstorage`: added missing `-inmemoryDataFlushInterval` command-line flag, which was missing in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) after implementing [this feature](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337) in [v1.85.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.0).
|
||||
* BUGFIX: `vmstorage`: properly expire `storage/prefetchedMetricIDs` cache. Previously this cache was never expired, so it could grow big under [high churn rate](https://docs.victoriametrics.com/FAQ.html#what-is-high-churn-rate). This could result in increasing CPU load over time.
|
||||
|
|
Loading…
Reference in a new issue