Skip to main content

Container image overview

The container images can be divided into the TWSC images provided by default and the custom images created based on the TWSC image:

TWSC images​

TWSC provides a variety of NGC optimized container images for AI computing and AI training frameworks as follows. Integrated with the TWSC GPU resources, container images help containers perform excellent computing performance.

TensorFlow, PyTorch, CUDA, Matlab (BYOL), Caffe, CNTK, MXNet, Caffe2, TensorRT, Triton Inference Server, Theano, Torch, DIGITS, NeMo, Clara Train SDK, RAPIDS, Merlin Training, HPC SDK, TAO Toolkit for Computer Vision, Modulus, Merlin Inference, and Clara Parabricks.

Refer to detailed image concept for more information on the AI training framework and package versions for each TWSC image.

  • Image name description​

    • Example：tensorflow-20.11-tf2-py3:latest
    • Description：AI Training framework-NGC release date (yy.mm)-Minor version defined by NGC-Python version:The latest adapted version of TWCC。
info
  • Most of the images correspond with the above name description, but a few of them are additionally marked with the applicable package name, e.g. digits-19.08-tensorflow:latest; or use the original version name of the image, e.g. matlab-r2019b:latest.
  • v1 indicates the optimized version of TWCC.
  • You can customize the identification tag for Custom Image instead of latest displayed in the image name.

  • Versions and features​

    • Container images: Only supported in versions after 19.08 (inclusive).
    • SSL encryption: Only supported in versions after 20.xx.
    • Jupyter Notebook: Only supported in versions after 20.xx.
    • Command log: For versions 21.08 and later, you can use the command history to view the logs

Custom images​

With custom images, you are able to keep the self-deployed container settings and packges built based on TWSC images. After the container image is created, all project members can share it. With this service, all software requires only one installation, providing you with the convenience of quickly copying and deploying the same environment.

Moreover, the billing starts when a container is created. You can create an image to store container settings and then delete it when the container is no longer needed to reduce your cost. Just restore the container from the image the next time you need it. In addition, you can use container images as a disaster recovery for container damage.