If you’re using Docker to run linkerd, there is no need to pull the release binary from GitHub, as described in the previous section. Instead, Buoyant provides the following public Docker images for you:
Both repositories have tags for all stable released versions of each image. To see a list of releases with associated changes, visit the linkerd GitHub releases page.
In addition to the versioned tags, the “latest” tag always points to the most recent stable release. This can be useful for environments that want to pick up new code without manually bumping the dependency version, but note that the latest tag may pull an image with breaking changes from a previous version, depending on the nature of the linkerd release.
Furthermore, the “nightly” tag is used to provide nightly builds of both linkerd and namerd from the most recent commit on the master branch in the linkerd GitHub repository. This image is unstable, but can be used for testing recently added features and fixes.
The default entrypoint for the linkerd image runs the linkerd executable, which requires that a linkerd config file be passed to it on the command line. The easiest way to accomplish this is by mounting a config file into the container at startup.
For instance, given the following config that simply forwards http requests received on port 8080 to the linkerd admin service running on port 9990:
admin: port: 9990 routers: - protocol: http dtab: /svc => /$/inet/127.1/9990; servers: - port: 8080
We can start the linkerd container with:
$ docker run --name linkerd -v `pwd`/config.yaml:/config.yaml buoyantio/linkerd:1.3.0 /config.yaml ... I 0922 02:01:12.862 THREAD1: serving http admin on /0.0.0.0:9990 I 0922 02:01:12.875 THREAD1: serving http on localhost/127.0.0.1:8080 I 0922 02:01:12.890 THREAD1: linkerd initialized.
Making sure it works
To verify that it’s working correctly, we can exec into the running container and curl linkerd’s admin ping endpoint via the http router’s configured port:
$ docker exec linkerd curl -s 127.1:8080/admin/ping pong
Success! For more information about linkerd’s admin capabilities, see the Administration page.