Chainguard Container for zipkin-slim

Smaller distribution of Zipkin which supports Elasticsearch storage and HTTP or gRPC span collection

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/zipkin-slim: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 Zipkin Slim image is comparable to the upstream Zipkin image. Switching to the Chainguard image should not require any changes to your existing setup.

Getting Started

You can start Zipkin Slim using the following command:

docker run -p 9411:9411 cgr.dev/ORGANIZATION/zipkin-slim:latest

Once the server is running, you can access the Zipkin UI at http://localhost:9411/zipkin.

You can configure your application to send traces with Zipkin instrumentation. The following is an example of using Zipkin with a Go application through OpenCensus.

Before running the application, make sure you have Go tools installed to build and run the sample application.

Create a main.go file to with the content from this GitHub repo

Initialize a new Go module:

go mod init myproject
go mod tidy

Once you have the code ready and Zipkin is running, run the application with the following command:

go run main.go

In the browser, open the URL http://localhost:8080/list and refresh the page as many times as you wish to generate a trace every time you hit the “/list” endpoint. You can also do it through a command line with curl http://localhost:8080/list

Go back to the Zipkin browser window and hit RUN QUERY; this will allow you to see the traces and inspect their details.

Documentation and Resources

• Zipkin on Docker
• Zipkin Tutorial
• Zipkin Docker Examples
• Zipkin instrumentation

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.