All Products
Search
Document Center

Container Compute Service:training-nv-pytorch 26.02

Last Updated:Aug 28, 2026

The training-nv-pytorch image bundles PyTorch and related training and inference libraries for workloads in Container Compute Service (ACS). Release 26.02 updates several of these libraries and provides CUDA variants for different NVIDIA driver versions and CPU architectures, so you can match the image to your nodes.

Main features and bug fixes

Main features

  • Upgraded DeepSpeed to version 0.18.5 and Transformers to version 4.57.6.

  • Upgraded vLLM to version 0.15.0 and flashinfer-python to version 0.6.1.

Bug fixes

None.

Known issues

None.

Contents

The following table lists the tags of the training-nv-pytorch 26.02 image and the requirements of each tag.

Item

26.02-cu130-serverless

26.02-cu128-serverless

Image name

training-nv-pytorch

training-nv-pytorch

Use cases

Training and inference

Training/Inference

Framework

pytorch

pytorch

CUDA version

13.0.2

12.8.0

Requirements

NVIDIA driver 580 or later

NVIDIA driver 575 or later

Supported architectures

amd64 and aarch64

amd64

Core components

26.02-cu130-serverless

  • Ubuntu: 24.04

  • Python: 3.12.7+gc

  • CUDA: 13.0

  • perf: 5.4.30

  • gdb: 15.0.50.20240403-git

  • torch: 2.9.0+ali.10.nv25.10

  • triton: 3.5.0

  • transformer_engine: 2.11.0+c188b533

  • deepspeed: 0.18.5+ali

  • flash_attn: 2.8.3

  • transformers: 4.57.6+ali

  • grouped_gemm: 1.1.4

  • accelerate: 1.11.0+ali

  • diffusers: 0.34.0

  • mmengine: 0.10.3

  • mmcv: 2.1.0

  • mmdet: 3.3.0

  • opencv-python-headless: 4.11.0.86

  • ultralytics: 8.3.96

  • timm: 1.0.24

  • vllm: 0.15.0+cu130

  • flashinfer-python: 0.6.1

  • pytorch-dynamic-profiler: 0.24.11

  • peft: 0.16.0

  • ray: 2.53.0

  • megatron-core: 0.15.0

26.02-cu128-serverless

  • Ubuntu: 24.04

  • Python: 3.12.7+gc

  • CUDA: 12.8

  • perf: 5.4.30

  • gdb: 15.0.50.20240403-git

  • torch: 2.9.0+ali.10.nv25.3

  • triton: 3.5.0

  • transformer_engine: 2.10.0+769ed778

  • deepspeed: 0.18.5+ali

  • flash_attn: 2.8.3

  • flash_attn_3: 3.0.0b1

  • transformers: 4.57.6+ali

  • grouped_gemm: 1.1.4

  • accelerate: 1.11.0+ali

  • diffusers: 0.34.0

  • mmengine: 0.10.3

  • mmcv: 2.1.0

  • mmdet: 3.3.0

  • opencv-python-headless: 4.11.0.86

  • ultralytics: 8.3.96

  • timm: 1.0.24

  • vllm: 0.15.0+cu128

  • flashinfer-python: 0.6.1

  • pytorch-dynamic-profiler: 0.24.11

  • peft: 0.16.0

  • ray: 2.53.0

  • megatron-core: 0.15.0

Driver requirements

The 26.02 release supports CUDA 12.8.0 and CUDA 13.0.2, and each CUDA version requires a different minimum NVIDIA driver version. The Contents section lists the driver requirement of each tag. For the complete list of supported drivers, see CUDA Application Compatibility. For more information, see CUDA Compatibility and Upgrades.

Assets

Pull the training-nv-pytorch 26.02 image from one of the following addresses. Select the tag that matches the NVIDIA driver version and CPU architecture of your nodes, as listed in the Contents section.

Public images

CUDA 13.0.2

egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:26.02-cu130-serverless

CUDA 12.8.0

egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:26.02-cu128-serverless

VPC images

Replace the public network registry host in your image URI with the region-specific VPC endpoint.

URI component

Public network

IN-VPC

Registry host

egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com

acs-registry-vpc.{region-id}.cr.aliyuncs.com

Repository

egslingjun

egslingjun (unchanged)

Image and tag

{image:tag}

{image:tag} (unchanged)

Replace {region-id} with the ID of the region where your ACS service runs. For example:

Region

Region ID

China (Beijing)

cn-beijing

China (Ulanqab)

cn-wulanchabu

For the full list of supported regions, see Regions.

Example {image:tag} values:

  • inference-nv-pytorch:25.10-vllm0.11.0-pytorch2.8-cu128-20251028-serverless

  • training-nv-pytorch:25.10-serverless

Note

This image applies to the ACS and Lingjun multi-tenant product forms. Do not use this image in Lingjun single-tenant scenarios.

Quick start

The following example shows how to pull the training-nv-pytorch image and start a container by using Docker.

Note

To use the training-nv-pytorch image in ACS, select the image on the Artifact Center page when you create a workload in the console. Alternatively, specify the image reference in a YAML file.

Usage notes

Review the following requirements before you run the training-nv-pytorch image:

  • The image contains changes to libraries such as PyTorch and DeepSpeed. Do not reinstall these libraries.

  • In the DeepSpeed configuration, leave zero_optimization.stage3_prefetch_bucket_size blank or set it to auto.

  • Adjust the built-in NCCL_SOCKET_IFNAME environment variable of this image based on your scenario:

    • If a single pod requests 1, 2, 4, or 8 GPUs for a training or inference job, you must set NCCL_SOCKET_IFNAME=eth0. This is the default configuration in this image.

    • If a single pod requests all 16 GPUs of a node for a training or inference job, you can use the HPN high-performance network. In this case, you must set NCCL_SOCKET_IFNAME=hpn0.

Step 1: Pull the image

Replace [tag] with the tag that matches the NVIDIA driver version and CPU architecture of your nodes, as listed in the Contents section.

docker pull egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:[tag]

Step 2: Start the container and run a training job

The training-nv-pytorch image includes a built-in model training tool named ljperf. The following example uses this tool to start a container and run a training job.

Note

Set NCCL_SOCKET_IFNAME based on the number of GPUs that a single pod requests, as described in the Usage notes section of this topic.

LLMs

# Start the container and connect to it
docker run --rm -it --ipc=host --net=host  --privileged egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:[tag]
# Run the training demo
ljperf benchmark --model deepspeed/llama3-8b

Step 3: Enable compilation and GPU memory optimization

Enable the following optimizations of the training-nv-pytorch image:

  • Enable compilation optimization: Use the Transformers Trainer API.

    training_args = TrainingArguments(
        bf16=True,
        gradient_checkpointing=True,
        torch_compile=True
    )
  • Enable GPU memory optimization for recomputation: Set the following environment variable.

    export CHECKPOINT_OPTIMIZATION=true

Key features and enhancements

The training-nv-pytorch image provides the following optimizations for PyTorch training. For the library changes introduced in 26.02, see the Main features and bug fixes section.

PyTorch compilation optimization

torch.compile(), introduced in PyTorch 2.0, often delivers strong gains for small-scale, single-GPU workloads. But LLM training depends on GPU memory optimization and distributed frameworks such as FSDP or DeepSpeed, so torch.compile() may offer limited benefits or even degrade performance.

  • Control communication granularity in the DeepSpeed framework. This helps the compiler capture a more complete compute graph and apply broader compilation optimizations.

  • Use an optimized PyTorch build:

    • The PyTorch compiler frontend is improved to ensure that compilation succeeds even if a graph break occurs in the compute graph.

    • Pattern matching and dynamic shape support are strengthened to improve post-compilation performance.

With these optimizations, 8B-parameter LLM training typically achieves an end-to-end throughput gain of about 20%.

GPU memory optimization for recomputation

A predictive model for GPU memory overhead, built on large-scale performance data—including different models, clusters, and training parameter settings, as well as system metrics such as GPU memory utilization collected during benchmarking—recommends the optimal number of activation recomputation layers. This approach is integrated into PyTorch, allowing you to achieve the performance gains of GPU memory optimization with minimal effort. This feature is now supported in the DeepSpeed framework.

End-to-end performance evaluation

The end-to-end performance of the training-nv-pytorch image was compared with the standard base image by using CNP, a cloud-native AI performance evaluation and analysis tool. The tests used mainstream open-source models and framework configurations. Ablation experiments were also run to measure how much each optimization component contributes to overall model training performance.

Image comparison against the base image and iterative evaluation

Performance comparison between this image and the base image across iterative evaluations

End-to-end performance contribution analysis of core GPU components

The following tests are based on the 26.02 image and evaluate and compare end-to-end training performance on a multi-node GPU cluster. The comparison items include:

  • Base: The NGC PyTorch image, which serves as the baseline.

  • ACS AI Image: Base+ACCL: The base image with the ACCL communication library.

  • ACS AI Image: AC2+ACCL: The golden image on AC2 BaseOS with the ACCL communication library and no optimization enabled.

  • ACS AI Image: AC2+ACCL+CompilerOpt: The golden image on AC2 BaseOS with the ACCL communication library and torch compile optimization enabled.

  • ACS AI Image: AC2+ACCL+CompilerOpt+CkptOpt: The golden image on AC2 BaseOS with the ACCL communication library, torch compile optimization, and selective gradient checkpoint optimization enabled.

End-to-end performance contribution of core GPU components