eclipse-mosquitto

packaged by Chainguard

Chainguard Container for eclipse-mosquitto

Eclipse Mosquitto - An open source MQTT broker

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/eclipse-mosquitto: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 eclipse-mosquitto image is comparable to the upstream eclipse-mosquitto image. It differs from upstream in the following ways:

• It ships no configuration file at /mosquitto/config/mosquitto.conf, so docker run without a mounted configuration exits with Error: Unable to open config file. The upstream image ships one that enables anonymous MQTT on port 1883, and the HTTP API with the bundled dashboard on port 9883. For quick testing, run docker run -p 1883:1883 cgr.dev/ORGANIZATION/eclipse-mosquitto /usr/sbin/mosquitto -c /mosquitto-no-auth.conf, which enables anonymous MQTT on port 1883.
• It does not include the dashboard.
• The broker is built without memory tracking, so it does not publish $SYS/broker/heap/current or $SYS/broker/heap/maximum, and memory_limit is accepted but not enforced.
• It is built without TLS-PSK. psk_file, psk_hint, bridge_identity, and bridge_psk only log a warning and are ignored, so a listener or bridge that relies on TLS-PSK alone starts without TLS.
• Upstream starts as root; this image runs as uid 1883, so PUID and PGID have no effect unless the container runs as root. Run as root, the broker drops to the uid in PUID, but the entrypoint gives /mosquitto to the mosquitto account rather than PUID:PGID, so the broker cannot write /mosquitto/data. Mounted volumes must be writable by the uid the broker runs as.

Getting Started

You can use the following config file to run the Eclipse Mosquitto image for quick testing:

cat <<EOF > mosquitto.conf
listener 1883
allow_anonymous true
EOF

Then, you can run the image with the following command:

docker run -d --name mosquitto -p 1883:1883 -v $(pwd)/mosquitto.conf:/mosquitto/config/mosquitto.conf cgr.dev/chainguard/eclipse-mosquitto:latest

That's it! You can now connect to the Mosquitto broker using an MQTT client.

To get more information about the configuration options, you can refer to the official Mosquitto Quick Start documentation.

Documentation and Resources

• Eclipse Mosquitto documentation
• Eclipse Mosquitto on GitHub

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.