Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Fix build of the ms-vscode.js-debug extension #82

Closed

Conversation

RomanNikitenko
Copy link
Contributor

Build of the ms-vscode.js-debug extension is failing with the following error:

/ms-vscode.js-debug-src/ms-vscode.js-debug/node_modules/dprint/dprint: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /ms-vscode.js-debug-src/ms-vscode.js-debug/node_modules/dprint/dprint)

At the moment:

  • ubi8/nodejs-18:1-102 is used to build the extension.
  • ubi8/nodejs-18:1-102 image contains GLIBC 2.28
  • ms-vscode.js-debug requires GLIBC 2.29

I didn't find ubi8-based image with the corresponding GLIBC version,
so I propose to try ubi9-based image - it contains 2.34version.

Copy link
Collaborator

@svor svor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend specifying the full image name directly in the Dockerfile as follows:
FROM registry.access.redhat.com/ubi9/nodejs-20:9.5

instead of using the ubi8Image attribute in plugin-config.json. The reason is that you’re using a UBI9 image, but the attribute name still references UBI8, which can cause confusion.

In general I don't remember why devspaces-code uses this Dockerfile to build the extension. Probably @mkuznyetsov should know something about that.

@RomanNikitenko RomanNikitenko force-pushed the fix-ms-vscode-js-debug-build branch from 0d05985 to fb8bad3 Compare December 17, 2024 14:41
@RomanNikitenko
Copy link
Contributor Author

@svor
I applied your suggestion, thank you for the review!

1 similar comment
@RomanNikitenko

This comment was marked as duplicate.

@RomanNikitenko RomanNikitenko force-pushed the fix-ms-vscode-js-debug-build branch from fb8bad3 to 907b033 Compare December 17, 2024 15:10
@RomanNikitenko
Copy link
Contributor Author

@svor @SDawley
Do we still use devspaces-3-rhel-8?
or
it make sense to close the current PR and open it for the devspaces-3-rhel-9 branch?

@SDawley
Copy link
Collaborator

SDawley commented Dec 17, 2024

Should be devspaces-3-rhel-9

@SDawley SDawley changed the base branch from devspaces-3-rhel-8 to devspaces-3-rhel-9 December 17, 2024 15:29
@SDawley SDawley changed the base branch from devspaces-3-rhel-9 to devspaces-3-rhel-8 December 17, 2024 15:29
@svor
Copy link
Collaborator

svor commented Dec 17, 2024

i think you need to make these changes for devspaces-3-rhel-9 and devspaces-3.18-rhel-9

@RomanNikitenko
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants