-
Notifications
You must be signed in to change notification settings - Fork 3
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
Incorrect volume path when using nginx volume override #61
Comments
@ttk I think this works as expected; the Essentially, once you get into overrides or making custom LMK if that makes sense or if I missed something! |
@reynoldsalec What is confusing for me is why behavior is different specifically for the For nginx:
Gets converted to the following raw docker compose spec (note the relative path):
Whereas if I do the same for the
I get the follow raw docker compose spec, where the volume source path was translated to the absolute path to my lando app root.
The translation of the relative paths to absolute path to my lando app root directory is what I expect for all services. I understand that using |
Apologies for the late response here. I'm wondering if this is something Windows specific, which sadly is not my area of expertise. I noticed that you're using quotes in the |
When adding an extra volume to the
appserver_nginx
container, the source directory on the host is wrong as it seems to be using the location of the underlying docker compose file location instead of my lando app root directory for the relative path. Best demonstrated by example:Simple lando config:
Expected bind mounts:
%LANDO_APP_ROOT%/vendor:/app/vendor
Actual bind mounts:
%USERPROFILE%/.lando/compose/test:/app/vendor
I tested the same scenario with the
nginx
lando plugin directly, and it mounted the expected directory, so I think it something to do with the way the symfony lando plugin integrates with nginx.OS: Windows 11 (not sure if that matters.
The text was updated successfully, but these errors were encountered: