-
Notifications
You must be signed in to change notification settings - Fork 28
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
Using .
for parent_dir causes issues
#57
Comments
Quick note: the expectation is that you use |
Mmm right, maybe my setup is weird. I'm working on something reproducible for others, so I don't want things in |
|
I'm not quite sure I follow. My steps were basically this:
That in return created If I'm standing at However, when I build the rootfs, the |
That might just be a bug. Relative paths should be resolved to absolute quite early, but maybe not everywhere/not correctly. |
Maybe using |
Yes, using the absolute paths seems to always work reliably. I'll do that for now and take a look at how the paths are resolved internally. |
I can’t reproduce the issue:
Can you provide updated steps to reproduce, ideally with a similarly self-contained transcript? |
When I try to use
--parent_dir .
things go wrong forExtraFilePaths
. At that point it no longer resolves relative paths by the instance/next to theconfig.json
, but seems to use the build directory instead.I suspect this is in the same ballpark as #50?
config.json
:Filesystem layout
Building with:
gok --parent_dir /home/daenney/Development/github.com/gotopi -i gotosocial overwrite --root root.squashfs
succeeds.Building with
gok --parent_dir . -i gotosocial overwrite --root root.squashfs
fails with:The text was updated successfully, but these errors were encountered: