-
Notifications
You must be signed in to change notification settings - Fork 638
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
Docker container name invalid on Mac when running with '-with-docker' flag #2528
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I can confirm this issue is also present in macOS Ventura. As correctly hinted by @arielromeo, the problem can be fixed by deleting line-break symbols from the generated base64-string using
(I could test this only by directly modifying the generated but failing The line-break symbols are added by the
For the context of this error, here is also the output from
And
|
I created a PR #4334 based on the above suggestion. I can't verify it because I don't use macOS, so if someone on this thread could test the PR that would be appreciated. |
I built the nextflow software based on the branch
Now I was able to successfully execute a simple workflow using Docker. 👍
Execution:
Thank you! 👏 |
Bug report
Expected behavior and actual behavior
Actual behavior when running with '-with-docker' flag is a failure because the docker name, which is stored in the variable 'NXF_BOXID' contains a carry return character '\r'.
The expected behavior is one such docker name is generated, it removes all the non-printable characters making a valid name.
Steps to reproduce the problem
This issue happens on MacOS Monterrey.
Program output
Environment
Additional context
I've chased this down to
nextflow/modules/nextflow/src/main/groovy/nextflow/executor/BashWrapperBuilder.groovy
Line 220 in ba22bdb
NXF_BOXID
gets appended with a '\r' character which breaks the docker run command.The presence of that char, can be seen in the output copied above:
The text was updated successfully, but these errors were encountered: