composer global require - executable file not found in $PATH about docker HOT 8 CLOSED

Can confirm that it works as expected now.

from docker.

I don't get what is going on exactly, however some things to note:

1. Output of composer gloabl require -vvv phpmetrics/phpmetrics is mostly identical, except for hashes.

2. VOLUME /composer (here) vs VOLUME /app (here)

FROM composer:1.2.2

RUN composer global require 'phpmetrics/phpmetrics'
RUN stat /composer/vendor

CMD [""]
ENTRYPOINT ["phpmetrics"]

gives stat: can't stat '/composer/vendor': No such file or directory here, whereas the directory exists when using composer/composer:1.1

4. Might be this from the Dockerfile reference section on VOLUME:

Note: If any build steps change the data within the volume after it has been declared, those changes will be discarded.

As the volume is declared in the base image and I extend it, my RUN command writes into the volume and the changes are discarded immediately.

5. Conclusion: I think /composer should not be annotated as VOLUME in the base image at all, so users can change its contents when extending from this image. A different use-case when this was desirable could be ADDing composer.* and running composer install during docker build for caching purposes.

from docker.

Thank you for reporting this and taking the time to thoroughly investigate the issue.

I am honestly not sure as to what the common conventions are regarding declaring volumes in official base images.

Perhaps it would be best if we did not declare a volume at all.

Please give me the time to get some feedback from some more experienced Docker folks before taking any actions. I will try to get back to you with an answer/solution asap :-)

from docker.

Thanks for the quick response :) I saw that you explained your line of thought in the original pull request but did not receive feedback on that in particular.

So it's probably best to get some expert knowledge here, happy to wait!

from docker.

@yosifkit | alcohol: We usually only declare volumes for things like database storage.

I'll drop the VOLUME declaration.

from docker.

@janpapenbrock the VOLUME declaration has been dropped, but it can take a while before the change gets merged. Keep an eye out :-)

from docker.

Awesome, thank you!

from docker.

Good to hear :-)

from docker.