Client-side Container Images

Use this page when you need Sauron-provided client images for log shipping or PushProx. This page is the source of truth for the image names, versions, and digests that Sauron publishes for customer-side use.

Images listed on this page are:

  • Built from source by Sauron team.
  • Built with tools obtained from trusted sources.
  • Based on hardened Oracle Linux container images that passed the latest vulnerability scan.
  • Publicly available from Oracle/OCI Container Registry.
Which image should I use?
Client image Use it for Start here
FluentBit Send logs to Sauron OpenSearch. Sending Logs
Prometheus PushProx Client Register scrape targets when Sauron Prometheus cannot directly reach your metrics endpoint. Sending Metrics - PushProx

For authentication choices, see User Access. For PushProx network patterns, see Shuttleproxy and the PushProx section in Sending Metrics.

Important Third Party Licensed Technology Approval Reminder

Sauron has acquired Third Party Licensed Technology approvals to distribute the images listed on this page to Sauron customers.

Sauron customers still need to acquire separate Third Party Licensed Technology approvals to use these images in production.

Before production

Before using a client image in production:

  1. Confirm the required Third Party Licensed Technology approval is complete.
  2. Pull the exact image and digest from this page.
  3. Confirm the client authentication method in User Access.
  4. Run the first log or PushProx validation flow before relying on production traffic.
  5. Keep the image name, tag, digest, command, and client logs for troubleshooting.
Available Images
FluentBit
Versions Images
4.2.2 docker pull container-registry.oracle.com/olcne/fluent-bit-base:v4.2.2@sha256:cfdfb194c66e729db1e8438976a238ad7718d25875d7fec357b5bb6eda65b670
Prometheus PushProx Client
Versions Images
0.2.0-102 docker pull phx.ocir.io/odx-sre/sauron/pushprox-mirror:0.2.0-102@sha256:3f0f0deaa79b45c243b033b418c85a0bb29fdac48422afb5e24a47e9b0b225de
Update cadence

This page is manually updated when a new client image is announced. Use the digest on this page when you need a reproducible pull command.

Self-check before escalation

Most client image questions can be resolved by checking the image, digest, workflow page, and client logs. If the image pull or client runtime does not behave as expected, check and collect:

  • Sauron URL.
  • Client image name, version, and digest.
  • Pull command used.
  • Runtime command or deployment method, with secrets removed.
  • Client platform.
  • Endpoint and authentication method.
  • Exact pull, startup, proxy, or client log error.
  • First failure time.
  • Recent image, credential, endpoint, or network changes.
  • Checks completed.
  • Production impact, if any.

Do not paste passwords, bearer tokens, private keys, or other secrets in Slack.