You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have created a custom image using the official Microsoft agent image and registered it as a self-hosted agent in Kubernetes 1.30. However, when we use this agent label for any Docker task or container section to pull the image from the registry and run it as a container, it fails due to Docker unavailability. We understand that Docker has been deprecated, and all supported Kubernetes versions on AKS use containerd as the default runtime starting from Kubernetes 1.19.
Is there any plan to support containerd as the default runtime for these tasks, rather than Docker, in future releases of the Azure DevOps pipeline Docker task?
Versions
4.248.0
--
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu
Version controll system
No response
Relevant log output
Task log
container:
image: ''
endpoint: ''
The text was updated successfully, but these errors were encountered:
What happened?
We have created a custom image using the official Microsoft agent image and registered it as a self-hosted agent in Kubernetes 1.30. However, when we use this agent label for any Docker task or container section to pull the image from the registry and run it as a container, it fails due to Docker unavailability. We understand that Docker has been deprecated, and all supported Kubernetes versions on AKS use containerd as the default runtime starting from Kubernetes 1.19.
Is there any plan to support containerd as the default runtime for these tasks, rather than Docker, in future releases of the Azure DevOps pipeline Docker task?
Versions
4.248.0 --Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu
Version controll system
No response
Relevant log output
Task log
container:
image: ''
endpoint: ''
The text was updated successfully, but these errors were encountered: