Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Zipkin is a distributed tracing system.
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.
Chainguard's Zipkin image is comparable to the upstream Zipkin image. Switching to the Chainguard image should not require any changes to your existing setup.
You can start Zipkin using the following command:
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:
Once you have the code ready and Zipkin is running, run the application with the following command:
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.
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 container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
BSD-3-Clause
Bitstream-Vera
FTL
GCC-exception-3.1
GPL-2.0-or-later
GPL-2.0-with-classpath-exception
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement