-
Notifications
You must be signed in to change notification settings - Fork 581
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
what's the current directory? #81
Comments
@jpmolinamatute Looks like the same issue as #90 and #51. Fyi, this will be solved through build-push-action v2 (#92) as it's written as a typescript-action to be as closed as possible of the GitHub Runner during its execution. You can already try it with: |
Version 2 has been merged to the main branch and is therefore available via As a reminder, this new version changes drastically and works with 3 new actions (login, setup-buildx and setup-qemu) that we have created. Many usage examples have been added to handle most use cases. And it should fix this current issue. Don't hesitate if you have any questions. |
@crazy-max I am still getting the same error on v2 |
@ThisIsQasim Can you create a new bug report please? Thanks. |
I investigated further and found that it wasn't cloning the repo. So I added a separate checkout action before the docker build and that fixed it. Not sure if that is the intended behavior or not. I can file a bug if not. |
Yes please. |
Hello World,
awesome GitHub action! this is a lifesaver. I'm getting this error
most likely is because I'm using a relative path and I'm missing a directory (or more)
any help would be appreciate it :-)
The text was updated successfully, but these errors were encountered: