Starting v10.3.0 nodejs 26 is included (before that was nodejs24). Starting nodejs 25+ became dynamically linked against libatomic.so.1, and that library is not present in jammy-base-stack (also checked full-stack, same here), as a result, my applications that triggered to update to the latest version got errors in runtime:
node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Expected Behavior
Well-tested compatibility with Packeto stack and new versions works well.
Current Behavior
Not well tested with the new versions of NodeJS
Possible Solution
Make CI tests to run and verify the packeto stack
Steps to Reproduce
Build an app with not pinned nodejs version and run it with the current paketobuildpacks/run-jammy-base image 27920d9fa0e57683c3333b879f64a877d66751e5a2eecaffc27bbaad5ed73c96
Starting v10.3.0 nodejs 26 is included (before that was nodejs24). Starting nodejs 25+ became dynamically linked against libatomic.so.1, and that library is not present in
jammy-base-stack(also checked full-stack, same here), as a result, my applications that triggered to update to the latest version got errors in runtime:Expected Behavior
Well-tested compatibility with Packeto stack and new versions works well.
Current Behavior
Not well tested with the new versions of NodeJS
Possible Solution
Make CI tests to run and verify the packeto stack
Steps to Reproduce
Build an app with not pinned nodejs version and run it with the current paketobuildpacks/run-jammy-base image 27920d9fa0e57683c3333b879f64a877d66751e5a2eecaffc27bbaad5ed73c96