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
Docksal aliases don't work within commands #974
Comments
What makes you think that alias does not work? As far as I see everything works. You have custom Dockerfile in one of your projects that has relative build path, that is not resolved properly because you use aliases.
You need to be mindful about relative paths when using aliases. |
@achekulaev I've gone through and made a more reproducible and simplified scenario, and this is still an issue. I can't start another project from within a command, and the config output is different as well. I've created two directories,
Here's the output of
And the diff for
And full config outputs: fin config outputs
And for good measure, Output of fin sysinfo output
Please try the above steps to reproduce and let me know how it goes. |
Thanks! |
Description
If you try to use a docksal alias within a docksal command, it fails.
This makes it hard to automate cross site interactions (at the most basic level, initializing one project as a dependency of another).
Steps to reproduce the issue:
Describe the results you received:
The project association is pretty scrambled.
Describe the results you expected:
The command successfully runs for the targeted environment (as happens running the command outside of another docksal command).
The text was updated successfully, but these errors were encountered: