-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Use relative paths in generated Dockerfile #3035
Conversation
Here I am, brain the size of a planet and they ask me to welcome you to Prefect. So, welcome to the community @pravindahal! 🎉 🎉 |
I think you still want to have the option for absoulte if you are using Docker for windows without SSH hence it should maybe be
|
@thomasfrederikhoeck I am using Docker for Windows using wsl2 backend. So, EDIT: Also, there is no downside to always having relative paths, IMO. |
@pravindahal it looks like your local git may not be authenticated with your github account (commits are showing up as grey octocat logo): If you want you could try this: Also going to tag @lauralorenz if she wants to test this windows side 🙂 |
@joshmeek Thanks for pointing out. My git client was using my company email, which I hadn't added to github. Fixed it now. |
@pravindahal I agree that there should be no downsides to relative paths. However it is worth noticing this comment (which leads me to suspect that someone has tried working on it before):
It might be worth testing out if the relative paths work on the legacy Hyper-V backend :-) |
@thomasfrederikhoeck I went back and found out the change here #2390 addresses the exact same issue. I will come back with an updated fix. |
I think I found the real problem, which is with the |
New PR here: #3044 |
Thanks for contributing to Prefect!
Please describe your work and make sure your PR:
changes/
directory (if appropriate)docs/outline.toml
for API reference docs (if appropriate)What does this PR change?
Before the fix, in the temporary Dockerfile that is created when using Docker storage for a flow, full paths to files are inserted. This causes docker build to fail as reported here: #3023