victorialogs-vlagent-fips

packaged by Chainguard

Chainguard Container for victorialogs-vlagent-fips

FIPS-enabled images for both VictoriaLogs and vlagent, providing high-performance, cost-effective log collection, storage, forwarding, and LogsQL querying with Fluent Bit, Logstash, OpenTelemetry, and Grafana integrations.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/victorialogs-vlagent-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This module publishes FIPS-enabled builds of two images from the VictoriaLogs source:

• cgr.dev/ORGANIZATION/victorialogs-fips corresponds to victoriametrics/victoria-logs:latest.
• cgr.dev/ORGANIZATION/victorialogs-vlagent-fips corresponds to victoriametrics/vlagent:latest.

Both Chainguard outputs are FIPS-enabled builds of the open-source tree, not aliases or rebuilds of the license-gated enterprise images. Both preserve their upstream entrypoints and / working directory and run as UID and GID 65532 instead of root. Mounted host paths must grant that user write access to /victoria-logs-data or /vlagent-data.

Because vlagent runs as nonroot while retaining the upstream / working directory, configure -tmpDataPath or -remoteWrite.tmpDataPath to use a writable mounted path such as /vlagent-data.

FIPS Support

This Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Running with Docker

Create a Docker network and run VictoriaLogs:

docker network create victorialogs
docker run -d --name victorialogs \
  --network victorialogs \
  -v victorialogs-data:/victoria-logs-data \
  -p 9428:9428 \
  cgr.dev/ORGANIZATION/victorialogs-fips:latest \
  -storageDataPath=/victoria-logs-data

Deploying with Helm

Create a values file for the official Helm chart:

cat > values.yaml <<'EOF'
server:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/victorialogs-fips
    tag: latest
EOF

helm install victorialogs victoria-logs-single \
  --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victorialogs --create-namespace \
  --values values.yaml

Forwarding with vlagent

Run vlagent-fips on the same Docker network:

docker run -d --name vlagent \
  --network victorialogs \
  -p 9429:9429 \
  -v vlagent-data:/vlagent-data \
  cgr.dev/ORGANIZATION/victorialogs-vlagent-fips:latest \
  -httpListenAddr=:9429 \
  -tmpDataPath=/vlagent-data \
  -remoteWrite.url=http://victorialogs:9428/insert/native

Deploying vlagent with Helm

Create a values file for the official victoria-logs-agent Helm chart:

cat > vlagent-values.yaml <<'EOF'
image:
  registry: cgr.dev
  repository: ORGANIZATION/victorialogs-vlagent-fips
  tag: latest
remoteWrite:
  - url: http://victorialogs-victoria-logs-single-server.victorialogs.svc.cluster.local:9428/insert/native
service:
  enabled: true
podSecurityContext:
  enabled: true
  fsGroup: 65532
securityContext:
  enabled: true
  runAsNonRoot: true
  runAsUser: 65532
EOF

helm install vlagent victoria-logs-agent \
  --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victorialogs --create-namespace \
  --values vlagent-values.yaml

Sending logs over TLS

Set REMOTE_WRITE_URL to a reachable HTTPS remote-write endpoint and CA_CERT to its CA certificate, then mount the certificate and configure vlagent to verify it:

docker run -d --name vlagent-fips-tls \
  -v vlagent-data:/vlagent-data \
  -v "${CA_CERT}:/tls/ca.crt:ro" \
  cgr.dev/ORGANIZATION/victorialogs-vlagent-fips:latest \
  -tmpDataPath=/vlagent-data \
  -remoteWrite.tlsCAFile=/tls/ca.crt \
  -remoteWrite.url="${REMOTE_WRITE_URL}"

Ingesting Logs

Insert logs using the JSON Lines format:

curl -X POST "http://localhost:9428/insert/jsonline" \
  -H "Content-Type: application/json" \
  -d '{"_msg":"Hello from VictoriaLogs","level":"info","app":"myapp"}'

Querying Logs

Query logs using LogsQL:

curl "http://localhost:9428/select/logsql/query?query=app:myapp"

Documentation and Resources

• VictoriaLogs Official Documentation
• LogsQL Query Language
• VictoriaMetrics Helm Charts
• VictoriaLogs Data Ingestion
• FIPS-enabled Chainguard Containers
• vlagent documentation
• VictoriaLogs Agent Helm chart

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.