-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
[email protected] not working in Github self-hosted actions, unable to override builder
option
#599
Comments
@tmf sorry for the inconvenience... Here the branch for the changes https://github.com/gperdomor/nx-tools/tree/feature/buildx-builder This change was made to fix an issue running parallels builds in gitlab... Maybe I can do the creation only if GitLab CI is detected or determined by a specific flag (I think the second option is better)... Do you know if this problem occurs only in self-hosted runners? or also happens on cloud runners?
Agree, it's a issue I will work on a new fix by the end of the week, please use 3.0.1 until the new version is released |
@tmf please try with version |
@gperdomor Thank you for the very quick fix! I can confirm
|
Closed and resolved in nx-docker 3.0.3 |
Thank you for providing this excellent NX plugin!
Unfortunately there seems to be an issue with the currently latest version
3.0.2
in the scenario of self-hosted Github actions runners.The build fails in self-hosted Github actions runners with the following error:
We were encountering a similar error already, as was explained in docker/setup-buildx-action#105,
The solution here was to use the following steps when setting up the
buildx
context:The
buildx
step would create a builder instance with this command:And this builder instance could be used in v2.x or up to
3.0.1
of@nx-tools/nx-docker
.However, with the new
builder
option, it always executes adocker buildx create --name
command, there is no possibility to not have a builder instance re-used from a previous step.Taken from
node_modules/@nx-tools/nx-docker/src/executor.js
(version3.0.2
)There are a couple of issues with the version
3.0.2
:Creating builder
step,options.builder
will always evaluatetrue
-ish due to the precedingoptions.builder = tempBuilder
blockoptions.builder
, ignoringINPUT_BUILDER
3.0.2
, I only could deduce this problem from inspecting the published npm package.The fix for now is to use
3.0.1
The text was updated successfully, but these errors were encountered: