-
Notifications
You must be signed in to change notification settings - Fork 133
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
composer.json file exists in current directory but composer is unable to find it (Windows 10) #114
Comments
what does Also not sure why you need the $@ there as there are no arguments to pass (I assume the snippet above is from a script and not being ran directly ? |
test changing |
Getting Docker working well under Windows 10 is a challenge. If you are using Docker under WSL2 then your files should be inside of the WSL environment; e.g. Using this setup, which is the recommended way to do things under WSL2 for maximum performance, the below is what I am getting on Windows 10, WSL2 Ubuntu 20. This:
did not work; I get:
This:
works for me, but only if you
That got me thinking, this is the only way I could get it to work from any directory:
This may offer future readers some assistance using the Dockerized composer image under WSL2, but I am still not able to use it for projects < php 8.0.2. See https://github.com/phpguru/docker-php-composer/tree/php7.4 |
Personally I use the following alias for composer: https://github.com/alcohol/dotfiles/blob/main/bin/composer In regards to PHP versions, please see our documentation: https://github.com/docker-library/docs/tree/master/composer#php-version--extensions |
Didn't mean to close this. |
I have the same problem running it as a Gitlab-CI job via docker-dind, I'm using this yml file, seems ok to me but gitlab-runner keeps saying there's no Can't provide access to the gitlab-runner, is in a place where only god knows how to reach from outside... and i doubt the IT guys would allow me to share. |
Try using single quotes. |
command being run:
output:
ls
output:The text was updated successfully, but these errors were encountered: