You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem here is that some python modules need to be installed to be able to be run.
Usually, pre-commit is able to do it on a single machine and this is not a big deal because it is done only once.
Running pre-commit in a container would mean that the container is re-built every time pre-commit is run. Hence probably too often.
We could evaluate whether adding the relevant volume bindings to the pre-commit image and gcc would help. But I tend to foresee complications moving forward.
My suggestion here would be to try to pre-bake an image with all the pre-commit tools inside it. Not sure how to do so though.
When trying to use this config:
I get this:
Smoking gun:
error: command 'gcc' failed: No such file or directory
This Dockerfile does not have
gcc
installed, and so therefore cannot be used with this action, or any that suffer the same issue.The text was updated successfully, but these errors were encountered: