Skip to content

[BUG]: Container Pipelines failing finding node24 path #5427

@tap1992

Description

@tap1992

What happened?

Since the agents in our Azure Managed DevOps pool auto updated to agent version 4.265.1, our pipelines that run within containers are now all failing with the below error on the first task that runs post initialise container, which in the example I'm showing below is: 'pre-job key vault extract'

OCI runtime exec failed: exec failed: unable to start container process: exec /__a/externals/node24/bin/node: no such file or directory: unknown
##[error]Exit code 126 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1002 -w /home/AzDevOps_azpcontainer 4a9cfd9be9af948bf09cd2f80e0bb2c9a21db141bde236696cff132b554ecef3 /__a/externals/node24/bin/node /__w/_temp/containerHandlerInvoker.js'.

Versions

Azure DevOps Services, Agent 4.265.1

I've ticked VMSS pool, but it is Azure Managed DevOps Pool

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 on host, Alpine 3.20 in the container

Version controll system

GIT

Relevant log output

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions