Skip to content
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

Closed
jpmolinamatute opened this issue Jul 29, 2020 · 7 comments
Closed

what's the current directory? #81

jpmolinamatute opened this issue Jul 29, 2020 · 7 comments
Milestone

Comments

@jpmolinamatute
Copy link

Hello World,

awesome GitHub action! this is a lifesaver. I'm getting this error

unable to prepare context: path "ai-tools/airflow" not found

most likely is because I'm using a relative path and I'm missing a directory (or more)

any help would be appreciate it :-)

@crazy-max
Copy link
Member

crazy-max commented Sep 2, 2020

@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:

@crazy-max crazy-max added this to the v2 milestone Sep 2, 2020
@crazy-max
Copy link
Member

Version 2 has been merged to the main branch and is therefore available via uses: docker/build-push-action@v2 (mutable tag).

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.

@ThisIsQasim
Copy link

@crazy-max I am still getting the same error on v2

@crazy-max
Copy link
Member

@ThisIsQasim Can you create a new bug report please? Thanks.

@ThisIsQasim
Copy link

ThisIsQasim commented Sep 12, 2020

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.

@crazy-max
Copy link
Member

@ThisIsQasim

I can file a bug if not.

Yes please.

@ThisIsQasim
Copy link

@crazy-max #120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants