-
Notifications
You must be signed in to change notification settings - Fork 19
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
Error: Cannot find module '@actions/core' #3
Comments
Hey there :) Might be totally wrong here, but I happen to reproduce the issue on act, but not when I run the action in a CI/CD pipeline. It seems to be related to this known bug. I'm going to play with it a bit and hopefully figure out a dirty workaround, but it probably won't be fun |
Alright, I'm interested to know if you find a solution. But if I gather correctly it is a problem with |
Not sure if the PR will be accepted, but nektos/act#288 should hopefully fix it :) It seems like a So long story short, it's probably affecting a lot of act users on various repos, but I'm no CI/CD veteran so I can't say for sure ^^ |
Thanks for investigating! Your analysis makes sense. The Sound to me like docker is doing something questionable here, especially since there doesn't seem to be an opt-out from this behavior [1]. Considering that there is no feasible work-around that we can implement on our side, I'm closing this issue here. Let's hope nektos/act#288 lands soon. Thanks again for investigating, and thanks for sending a fix to [1] https://docs.docker.com/engine/reference/commandline/cp/#options |
just FYI the act pull request landed, so I hope it helps :) |
Awesome, thanks for letting us know :) And nice to see a test with |
Hi there
I'm using https://github.com/nektos/act for local crafting / debuguing of my GitHub Actions.
It's π₯ 'ing like this
Can you give me an hint about what went wrong ?
If you want to reproduce, I'm using act 0.2.8 (~ latest) with the command
act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 -s GIT_CREDENTIALS=https://me:mytoken@github.com
(warning, this docker image is ~18G big) and here's my workflowThe text was updated successfully, but these errors were encountered: