[loong64] Fixed the "The GID `1000' is already in use" error.#186
[loong64] Fixed the "The GID `1000' is already in use" error.#186rvagg merged 1 commit intonodejs:mainfrom
Conversation
If the group/user with the specified GID/UID already exists, it will be changed to node:node. similar to recipes/riscv64/Dockerfile.
rvagg
left a comment
There was a problem hiding this comment.
gee, that's a bit overcomplicated, but I guess we have precedent
|
@rvagg Would it be possible to re-trigger the image build? I'd really appreciate your help with this! |
|
Keep an eye on that github-webhook.log and report back here if everything builds successfully; then I can go and trigger a build |
|
sorry github-webhook.log wasn't being recreated, I had to give it a kick but the contents got lost - but the container built successfully and I kicked off a new build of the latest Node, happening here and will hopefully appear for download if it finishes successfully: https://unofficial-builds.nodejs.org/logs/202509021408-v24.7.0/loong64.log |
@rvagg I see that the loong64 build has completed successfully. |
If the group/user with the specified GID/UID already exists, it will be changed to node:node.
similar to recipes/riscv64/Dockerfile.
Reopened builds for node versions >= 23.
Since simdutf has not been updated to version 6.2.1 or higher, building for version 18 has been disabled.