Docker installation

Container-based options

Since RADKit 2.0.0, hardened “distro-less” Docker images are available for download for both RADKit Service (without Client) and RADKit Client (with Service, to support integrated mode). These images are meant to be run as-is, and in particular, they do not include a shell and are not meant to be extended or used as the basis for another image.

It is also possible to build your own Docker image with the RADKit components of your choice, based on the Python wheels available from the PyPI index or the downloads area. For RADKit Service, specific instructions and scripts are provided at Running Service in Docker.

Note

Cisco internal users can also find pre-built RADKit Docker images for Linux in this repository, with the latest tag pointing to the latest stable external release. You need to be connected to the Cisco network in order to access the repository and pull images. Those images are for internal use only and may not be published externally under any circumstances.

Downloading the images

Please visit the downloads area and locate the latest RADKit container image archives for your platform. The archives are named radkit-<APP>-hardened_<PLATFORM>_<VERSION>.tgz and the signature file is named cisco_radkit_<VERSION>.sig256, where:

  • <APP> is either client (Client + Service) or service (Service only);

  • <PLATFORM> is either linux_amd64 or linux_arm64;

  • <VERSION> is the RADKit version that you are downloading.

For example, for version 2.0.0, the available images are:

  • radkit-client-hardened_linux_amd64_2.0.0.tgz

  • radkit-client-hardened_linux_arm64_2.0.0.tgz

  • radkit-service-hardened_linux_amd64_2.0.0.tgz

  • radkit-service-hardened_linux_arm64_2.0.0.tgz

Installing the images

Danger

All RADKit releases available externally are cryptographically signed by Cisco. The signature of the Docker container image archives must be verified manually (please refer to Code signing for more information). Never install unsigned or unverified software !

These files can be imported into Docker using the command:

docker image load -i <image-tarball-file>

For example, to run RADKit Client interactively on ARM:

$ docker image load -i radkit-client-hardened_linux_arm64_2.0.0.tgz
$ docker run --rm -it -v /tmp/radkit:/radkit radkit-client-hardened:2.0.0