Chainguard Image for monstache

A go daemon that syncs mongodb to elasticsearch in realtime.

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/monstache:latest

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

Compatibility Notes

Chainguard's Monstache image is a Wolfi-based container image. It is comparable to the Monstache image published by RWynn in functionality and has minimal dependencies. Similar to the rwynn/monstache image, this image does not come with any default configuration.

Getting Started

Monstache is a Go daemon that syncs MongoDB to Elasticsearch in real time. It is designed for MongoDB 3.6+ and Elasticsearch 7.0+. It uses the official MongoDB golang driver and the community supported Elasticsearch driver from olivere.

Using Monstache with Docker

Let say you have a monstache.config.toml file in your current working directory. In order for the container to work and sync with your MongoDB and Elasticsearch instances, you need to mount your custom monstache.config.toml file in the container. The following example runs Monstache with a custom configuration file:

docker run -it --rm -v "$(pwd)/monstache.config.toml:/monstache.config.toml" cgr.dev/ORGANIZATION/monstache -f monstache.config.toml

Using Monstache with Kubernetes

You can also run Monstache as a pod in your Kubernetes setup. In order for the pod to work properly and sync with your MongoDB and Elasticsearch pods, you would need to create a configmap with your custom monstache.config.toml and mount that configmap in your Monstache pod. The following example runs Monstache as a pod with a configmap containing your custom configuration file:

---
apiVersion: v1
kind: Pod
metadata:
  name: monstache-demo
spec:
  containers:
  - name: monstache
    image: cgr.dev/ORGANIZATION/monstache
    command: ["/bin/monstache", "-f", "monstache.config.toml"]
    volumeMounts:
      - name: config-volume
        mountPath: /monstache.config.toml
        subPath: monstache.config.toml
  volumes:
    - name: config-volume
      configMap:
        name: monstache-config
        items:
        - key: monstache.config.toml
          path: monstache.config.toml
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: monstache-config
data:
  monstache.config.toml: |
    # Your monstache configuration here

Documentation and Resources

Please refer to the official Monstache site for more information on configuration and usage.

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.