Docker setup failing with error "Initiated Worker with invalid execArgv flags" #16379
Labels
Comments
|
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
jupyterlab-probot
bot
added
the
status:Needs Triage
|
In the docker logs do you see which version of Node.js is used? |
|
@krassowski thanks again. as you can see there is only the command that is specified in the docker file which is: |
|
This looks like a potential regression from #15909 - I note that the CC @fcollonval in case if you have suggestions as author of #15909 |
|
Previously it was using |
|
Hey this looks like a damn bad issue in NodeJS: nodejs/node#41103 nodejs/node#53011 That said, I don't have any idea right now to fix the issue. One possibility, would be to install a more recent version of node.js by changing the spec in that line: Line 35 in b2ff3fb for example to A question for @kiansahafi , are you using vscode? If yes, could you test to open the folder using the dev container? FYI, yarn is using jlpm as can be seen in the error trace: This is the consequence of that configuration: Line 25 in b2ff3fb But we cannot use |
JasonWeill
removed
the
status:Needs Triage
JasonWeill
changed the title
|
@kiansahafi Thank you for your contribution! The related Node issues are not macOS-specific, so I retitled the issue to emphasize the error. |
|
Thanks @fcollonval for the advice. for nodejs=22:
for nodejs=20: |
|
v22 is not on conda-forge yet indeed - https://github.com/conda-forge/nodejs-feedstock/ I would hope the fix gets released in v20.3 whenever/if it gets published. |
Ok that is a good news - the start script wants to be too smart. Would you mind running another test by executing the following command within the root folder of the repository: docker build --no-cache --build-arg NEW_MAMBA_USER_ID=$(id -u) --build-arg NEW_MAMBA_USER_GID=$(id -g) . -f docker/Dockerfile
|
|
@fcollonval i tried this specific command:
-BTW i noticed that each of the dependencies(e.g. babel, nrwl, mhchemparser, lib0, wrappy & ...) give this error individually and then the build fails. not sure if it makes a difference.
|
|
@kiansahafi was this with a docker file modified to use nodejs v20? |
|
@krassowski No, I changed it back to the original version of the dockerfile. (which is I tested it with |
|
Thanks for the test @kiansahafi For what I saw, yarn is using a workers pool to handle the fetched packages. This is consistent with your finding that each dependency gives the same error. One more question, when using vscode devcontainer, does the command |
|
not a problem @fcollonval, i don't know how to check that.
|
Actually what I'm interested in, is what happen if you execute within that image |
|
@fcollonval i attached to the container and in the root directory i found a and i executed the
i also have access to the logs of the terminal when vscode starts but there is no sign of anything not |
|
Hey @kiansahafi thanks for keeping testing. I made a short demo of what I would like you to test - I guess it will be easier than explaining: jlpm-in-docker.mp4Note Attaching to the vscode container may not work if you did not start the docker as they do. |
|
thanks @fcollonval for the detailed video and notes. 😅
Screen.Recording.2024-05-31.at.12.39.09.mp4
|
|
Thanks again for the test @kiansahafi The appearance of the error in the dev container is at least consistent (the dev container is actually not running the last part of the Dockerfile). But finding a solution is gonna be hard. |
|
@fcollonval not a problem.😁 If there's any way I can help/contribute, that would be awesome. Thanks again! |
|
Last idea, in the docker, could you report the defined environment variables ? You should get that list by executing Important Check that there are no sensitive information in them before posting that list here 😉 |
|
@fcollonval not a problem. thanks for the heads up 😁 this is the result of executing |
|
Thanks @kiansahafi Unfortunately nothing out of the ordinary there. |
|
What do you get when executing: for reference I got |
|
@fcollonval i get the same thing: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
i am trying to build the project (with my M1 mac) using the docker file in
/docker/start.shusing this command:bash docker/start.shit fails to builds giving this error:
docker build Error at Line:
complete Error:
the above issue repeats many times, until the docker build fails...
Reproduce
execute this command on an M1 mac:
bash docker/start.shExpected behavior
build successfully without any error and create a new docker image.
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: