[BUG]: Warning! Using Node 20 for container startup.

[kllysng]

What happened?

We are getting tons of warnings in our builds ##[warning]Using Node 20 for container startup.

This warning appears under another regular log container-startup-using-node-20.

Why are we being notified twice? Why is one of them a warning? They're quite noisy.

Versions

v20.19.4

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

No response

Version controll system

No response

Relevant log output

v20.19.4
 container-startup-using-node-20
##[warning]Using Node 20 for container startup.

[JoeRobich]

We are also seeing this in dotnet/vscode-csharp (Example run)

[wmpires]

Hi,

The warning originates from the Initialize containers step within the jobs executed on the Azure Pipeline. Specifically, it is triggered by this file: https://github.com/microsoft/azure-pipelines-agent/blame/b1ecea75b3903fb9da050429d6049f5b7258c4ad/src/Agent.Worker/ContainerOperationProvider.cs#L653

I'm unsure whether this warning is intended to be permanent or not, however, the solution is quite simple:

• Supply your own copy of Node.js.
• Add a label to your image pointing to the location of the Node.js binary.

For further details, refer to the official documentation: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops&tabs=linux#nonglibc-based-containers

Best regards,

[rajmishra1997]

Solution provided in comments

[aagor]

We are seeing this issue on glibc-based containers, too.

The screenshot and linked documentation only talks about non-glibc-based containers, therefore the solutions seems not applicable.
Can this issue be reopened?

[akoeplinger]

I see there were some changes that sound related to this in #5450, @rajmishra1997 mind confirming whether these address this issue?

[kllysng]

I see a PR and that the issue is closed, but we still are seeing the noisy warnings fyi.