packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Eclipse Zenoh router (zenohd) with the REST and storage-manager plugins
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
This image provides zenohd, the router daemon of Eclipse Zenoh, with the REST and storage-manager plugins. It is licensed under EPL-2.0 OR Apache-2.0, and is designed as a drop-in replacement for the upstream eclipse/zenoh image:
/entrypoint.sh. It prints itself, then runs /$BINARY with the supplied arguments (BINARY=zenohd, RUST_LOG=info). The script is taken from upstream's image build, except that it quotes "$@", so arguments containing spaces reach zenohd intact./zenohd and /usr/bin/zenohd. The plugins are installed in /usr/lib, which is in zenohd's default plugin search path, and are also linked at upstream's /libzenoh_plugin_rest.so and /libzenoh_plugin_storage_manager.so, so configs that name them by __path__ keep working.zenohd is built with the same Rust toolchain as upstream, because zenohd refuses to load plugins built with a different rustc.*-unknown-linux-gnu target against the same zenoh version and features, with the rustc release that zenohd --version reports.libstdc++, so custom plugins that link C++, such as a RocksDB storage backend, can load./root/.zenoh (plugins in its lib/); here HOME is /home/nonroot, so mount the same directory, readable by UID 65532, at /home/nonroot/.zenoh, or the plugins themselves into /usr/local/lib.The image listens on the same ports as upstream: 7446/udp for multicast scouting, 7447/tcp for the zenoh protocol, and 8000/tcp for the REST API (only when the REST plugin is enabled). Unlike upstream, the image declares no exposed ports, so docker run -P publishes nothing; publish ports with -p.
Print the version:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
Start a router with the REST API and an in-memory storage for demo/**, then write and read a value:
zenohd takes a JSON5 configuration file with -c, and single settings with --cfg KEY:VALUE. Write a file, mount it, and point zenohd at it. The file must be readable by UID 65532:
Upstream's DEFAULT_CONFIG.json5 documents every option with its default. See also the configuration reference.
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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at Chainguard