composer home directory not writable when running as custom user about docker HOT 6 CLOSED

It should be soon. docker-library/docs#981

from docker.

Maybe we can use something like --volume ~/.composer/cache:/composer/cache:rw to enable the cache?

from docker.

I defaulted the COMPOSER_HOME to /tmp in the image template. The next release should see this change. So in future release (> 1.4.2) you can do --volume ~/.composer/cache:/tmp/cache:rw.

I chose this solution because /tmp generally does not have any permission issues.

from docker.

I see. BTW, is there a way to change the default packagist source globally? I have to make a new image adding RUN composer config -g repo.packagist composer https://custom.packagist.source

from docker.

Your solution is the only way to make it an explicit default in the image/container itself.

Alternatively, you can mount your Composer home directory (~/.composer usually) onto /tmp inside the image (assuming the composer configuration on your host has this desired default changed).

from docker.

This change is not yet reflected in the docs.

from docker.