microsoft/Oryx

Release 20240312.3 doesn't support node 18.19.1

bh3605 opened this issue · 2 comments

Bug Report

Release 20240312.3 doesn't support 18.19.1 even though it says it does.

  • At what date and time did you most recently experience the problem?
    3/15/24

  • Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.
    Azure Devops YAML Build Pipeline

  • What happened?
    glib c error

  • What did you expect or want to happen?
    It would build my node repo

  • How can we reproduce it?
    Build an Angular 17 project. Set the container and environment vars

container: 'mcr.microsoft.com/oryx/build:20240312.3'
DEBIAN_FLAVOR: "bullseye"
NODE_VERSION: 18.19.1

  • Do you have log output? Please include between the backticks:
Starting: Build
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.236.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
##[warning]The container operating system doesn't support Node20. Using Node16 instead. Please upgrade the operating system of the container to remain compatible with future updates of tasks: https://github.com/nodesource/distributions
Generating script.
Script contents:
oryx build /__w/1/s/ --output /__w/1/a
========================== Starting Command Output ===========================
/bin/bash --noprofile --norc /__w/_temp/1a5a0ff5-fd22-4c41-a34b-bcd099e0dcea.sh
Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20240312.3, Commit: 9de9485111477058fd0c4753e00d686436cf4bf1, ReleaseTagName: 20240312.3

Build Operation ID: 8333363f63cb3725
Repository Commit : 20024168779deb8c04da481b988d656d2df94b95
OS Type           : bullseye
Image Type        : full

Detecting platforms...
Detected following platforms:
  nodejs: 18.19.1
Version '18.19.1' of platform 'nodejs' is not installed. Generating script to install it...
Detected the following frameworks: Angular,Typescript


Source directory     : /__w/1/s
Destination directory: /__w/1/a


Downloading and extracting 'nodejs' version '18.19.1' to '/tmp/oryx/platforms/nodejs/18.19.1'...
Detected image debian flavor: bullseye.
Downloaded in 1 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: nodejs...
Done in 2 sec(s).

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Using Node version:
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
##[error]Bash exited with code '1'.
Finishing: Build

Tagging @william-msft since the auto assign workflow failed

@simonjj There are several open issues w/o comments from anyone who works on this repository yet I still see commits and releases. Is anyone looking at these issues?