-
Notifications
You must be signed in to change notification settings - Fork 13
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
Conversation
There was a problem hiding this 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.
0d05985
to
fb8bad3
Compare
@svor |
1 similar comment
This comment was marked as duplicate.
This comment was marked as duplicate.
Signed-off-by: Roman Nikitenko <[email protected]>
fb8bad3
to
907b033
Compare
Should be devspaces-3-rhel-9 |
i think you need to make these changes for devspaces-3-rhel-9 and devspaces-3.18-rhel-9 |
Build of the
ms-vscode.js-debug
extension is failing with the following error:At the moment:
ubi8/nodejs-18:1-102
is used to build the extension.ubi8/nodejs-18:1-102
image contains GLIBC2.28
ms-vscode.js-debug
requires GLIBC2.29
I didn't find
ubi8
-based image with the correspondingGLIBC
version,so I propose to try
ubi9
-based image - it contains2.34
version.