Document global install changes since 1.4.2 about docker HOT 8 CLOSED

I think you mean that the default home directory changed?

This change should only impact a very small subset of users. I am sorry for the inconvenience it might have caused you though. You are indeed correct that the current documentation is not up to date. I will remedy this tomorrow.

from docker.

Yes, in so fewer words. 😊

Thank you for the prompt consideration!

from docker.

The docs should now be up to date. If you have anything to add, please let me know.
Otherwise, can we consider this issue resolved?

from docker.

Eh, sorry for writing to closed issue, but I didn't anything about this in documentation. I had working script in docker (Gitlab CI probably selected the latest version of container):

composer global require justinwalsh/daux.io
daux --source=docs --destination=public

Latest successful build has been 4th August 2017, after that, I getting daux: command not found.
I fixed it by export PATH=$PATH:/tmp/vendor/bin/, but I think it will be good to export PATH automatically.

from docker.

I am missing sufficient context to understand how your issue is related exactly.

from docker.

@alcohol In older versions of container (probably 1.4.2), the PATH environment variable contains composer's global bin directory. After changing composer's global path (1.4.3+), the PATH environment variable doesn't contains valid path to composer's global bin directory, so I can't launch for sample daux command without adding composer's global bin path to PATH environment variable.

from docker.

That is highly unlikely, as we never set the PATH environment variable to anything specifically, and the default PATH does not include the composer global bin directory. Are you using our image directly? Or have you extended it using your own Dockerfile?

from docker.

I am sorry, I just double checked and I stand corrected. In older versions we did use ENV PATH "/composer/vendor/bin:$PATH". We stopped doing this because global installs inside a container make no sense anyway.

The Composer container should be considered a throw-away tool. You run it against a volume bind and then destroy it once it has completed its task. If you really need to set the PATH and such, you can do so yourself.

We removed most defaults because preferably our Container leaves as much as possible up to the end user to decide. We merely set the absolute minimum required to run the Container hassle free.

from docker.