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
Not a bug and not a feature, but an ask. Could someone please update the packages inside the ubuntu docker image used for the agent? It's woefully out of date and while one might argue that most of the outdated packages are irrelevant, there are some which are notable, for example azure-cli, which is still on some 2.0 version from 2019. Things such as federated logins do not work on this version and it is very cumbersome to have to manually go in and update all packages after updating the image tags to newer agent versions.
With kind regards!
Versions
All docker versions of the agent
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)
Operation system
No response
Version controll system
No response
Azure DevOps Server Version (if applicable)
No response
The text was updated successfully, but these errors were encountered:
@bufnitza, could you specify which Ubuntu image you are referring to? I assume it's when attempting to run the Azure Pipelines Agent in the docker container, correct?
@ivanduplenskikh I'm referring to the images built by Microsoft and pushed to mcr.microsoft.com/azure-pipelines/vsts-agent
After opening this ticket, I also bumped into the article you shared and after discussing with the team, we'll probably switch to our locally built agents, as per those instructions. The above still remains valid, but I'm not sure what the support policy is for those images on the MCR.
Describe your question
Hello team,
Not a bug and not a feature, but an ask. Could someone please update the packages inside the ubuntu docker image used for the agent? It's woefully out of date and while one might argue that most of the outdated packages are irrelevant, there are some which are notable, for example
azure-cli
, which is still on some 2.0 version from 2019. Things such as federated logins do not work on this version and it is very cumbersome to have to manually go in and update all packages after updating the image tags to newer agent versions.With kind regards!
Versions
All docker versions of the agent
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Operation system
No response
Version controll system
No response
Azure DevOps Server Version (if applicable)
No response
The text was updated successfully, but these errors were encountered: