Support Policy - AWS Deep Learning Containers
Supported FrameworksFrequently Asked Questions

Support Policy

AWS Deep Learning Containers (DLCs) simplify image configuration for deep learning workloads and are optimized with the latest frameworks, hardware, drivers, libraries, and operating systems. This page details the framework support policy for DLCs.

Supported Frameworks

Reference the following AWS Deep Learning Containers Framework Support Policy table to check which frameworks and versions are actively supported.

Refer to End of patch to check how long AWS supports current versions that are actively supported by the origin framework’s maintenance team. Frameworks and versions are available in single-framework DLCs.

Note

In the framework version x.y.z, x refers to the major version, y refers to the minor version, and z refers to the patch version. For example, for TensorFlow 2.6.5, the major version is 2, the minor version is 6, and the patch version is 5.

Frequently Asked Questions

What framework versions get security patches?

If the framework version is labeled Supported in the AWS Deep Learning Containers Framework Support Policy table, it gets security patches.

What images does AWS publish when new framework versions are released?

We publish new DLCs soon after new versions of TensorFlow and PyTorch are released. This includes major versions, major-minor versions, and major-minor-patch versions of frameworks. We also update images when new versions of drivers and libraries become available. For more information on image maintenance, see When does active support for my framework version end?

What images get new SageMaker/AWS features?

New features typically release in the latest version of DLCs for PyTorch and TensorFlow. Refer to the release notes for a specific image for details on new SageMaker or AWS features. For a list of available DLCs, see Release Notes for AWS Deep Learning Containers. For more information on image maintenance, see When does active support for my framework version end?

How is current version defined in the Supported Frameworks table?

The current version in the AWS Deep Learning Containers Framework Support Policy table refers to the newest framework version that AWS makes available on GitHub. Each latest release includes updates to the drivers, libraries, and relevant packages in the DLC. For information on image maintenance, see When does active support for my framework version end?

What if I am running a version that is not in the Supported Frameworks table?

If you are running a version that is not in the AWS Deep Learning Containers Framework Support Policy table, you may not have the most updated drivers, libraries, and relevant packages. For a more up-to-date version, we recommend that you upgrade to one of the supported frameworks available using the latest DLC of your choice. For a list of available DLCs, see Release Notes for AWS Deep Learning Containers.

Do DLCs support previous versions of TensorFlow?

No. We support the latest patch version of each framework’s latest major version released 365 days from its initial GitHub release as stated in the AWS Deep Learning Containers Framework Support Policy table. For more information, see What if I am running a version that is not in the Supported Frameworks table?

How can I find the latest patched image for a supported framework version?

To use a DLC with the latest framework version, browse the DLC GitHub release tags to find the sample image URI of your choice and use it to pull the latest available Docker image. The framework version that you choose must be labeled Supported in the AWS Deep Learning Containers Framework Support Policy table.

How frequently are new images released?

Providing updated patch versions is our highest priority. We routinely create patched images at the earliest opportunity. We monitor for newly patched framework versions (ex. TensorFlow 2.9 to TensorFlow 2.9.1) and new minor release versions (ex. TensorFlow 2.9 to TensorFlow 2.10) and make them available at the earliest opportunity. When an existing version of TensorFlow is released with a new version of CUDA, we release a new DLC for that version of TensorFlow with support for the new CUDA version.

Will my instance be patched in place while my workload is running?

No. Patch updates for DLC are not “in-place” updates.

You must delete the existing image on your instance and pull the latest container image without terminating you instance.

What happens when a new patched or updated framework version is available?

Regularly check the release notes page for your image. We encourage you to upgrade to new patched or updated frameworks when they are available. For a list of available DLCs, see Release Notes for AWS Deep Learning Containers.

Are dependencies updated without changing the framework version?

We update dependencies without changing the framework version. However, if a dependency update causes an incompatibility, we create an image with a different version. Be sure to check the Release Notes for AWS Deep Learning Containers for updated dependency information.

When does active support for my framework version end?

DLC images are immutable. Once they are created they do not change. There are four main reasons why active support for a framework version ends:

Note

Due to the frequency of version patch upgrades and security patches, we recommend checking the release notes page for your DLC often, and upgrading when changes are made.

Framework version (patch) upgrades

If you have a DLC workload based on TensorFlow 2.7.0 and TensorFlow releases version 2.7.1 on GitHub, then AWS releases a new DLC with TensorFlow 2.7.1. The previous images with 2.7.0 are longer actively maintained once the new image with TensorFlow 2.7.1 is released. The DLC with TensorFlow 2.7.0 does not receive further patches. The DLC release notes page for TensorFlow 2.7 is then updated with the latest information. There is no individual release note page for each minor patch.

New DLCs created due to patch upgrades are designated with updated release tags. If changes are not backwards compatible, the tag will change major versions rather than minor versions (ex. v1.0 will change to v2.0 rather than v 1.2).

AWS security patches

If you have a workload based on an image with TensorFlow 2.7.0 and AWS makes a security patch, then a new version of the DLC is released for TensorFlow 2.7.0. The previous version of the images with TensorFlow 2.7.0 is no longer actively maintained. For more information, see Will my instance be patched in place while my workload is running? For steps on finding the latest DLC, see How can I find the latest patched image for a supported framework version?

New DLCs created due to patch upgrades are designated with updated release tags. If changes are not backwards compatible, the tag will change major versions rather than minor versions (ex. v1.0 will change to v2.0 rather than v 1.2).

End of patch date (Aging out)

DLCs hit their end of patch date 365 days after the GitHub release date.

Important

We make an exception when there is a major framework update. For example. if TensorFlow 1.15 updates to TensorFlow 2.0, then we continue to support the most recent version of TensorFlow 1.15 for a period of two years from the date of the GitHub release or six months after the origin framework maintenance team drops support, whichever date is earlier.

Dependency end-of-support

If you are running a workload on a TensorFlow 2.7.0 DLC image with Python 3.6 and that version of Python is marked for end-of-support, then all DLC images based on Python 3.6 will no longer be actively maintained. Similarly, if an OS version like Ubuntu 16.04 is marked for end-of-support, then all DLC images that are dependent on Ubuntu 16.04 will no longer be actively maintained.

Will images with framework versions that are no longer actively maintained be patched?

No. Images that are no longer actively maintained will not have new releases.

How do I use an older framework version?

To use a DLC with an older framework version, browse the DLC GitHub release tags to find the image URI of your choice and use it to pull the docker image.

How do I stay up-to-date with support changes in frameworks and their versions?

Stay up-to-date with DLC frameworks and versions using the DLC release notes, and the Available Deep Learning Containers Images page.

Do I need a commercial license to use the Anaconda Repository?

Anaconda shifted to a commercial licensing model for certain users. Actively maintained DLCs have been migrated to the publicly available open-source version of Conda (conda-forge) from the Anaconda channel.

Warning

If you are actively using Anaconda to install and manage your packages and their dependencies in a DLC that is no longer actively maintained, you are responsible for complying with the governing license from the Anaconda Repository, if you determine that the terms apply to you. Alternatively, you can migrate to one of the currently-supported DLCs listed in the AWS Deep Learning Containers Framework Support Policy table or you can install packages using conda-forge as a source.