docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Apply markdownfmt

This commit is contained in:
Tianon Gravi 2019-02-26 12:20:42 -08:00
parent bc5cd482ec
commit 5accd167e8
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
composer/content.md
View File

@ -13,7 +13,7 @@ You can read more about Composer in our [official documentation](https://getcomp
Running the `composer` image is as simple as follows:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
%%IMAGE%% install
```
@ -23,7 +23,7 @@ docker run --rm --interactive --tty \
You can bind mount the Composer home directory from your host to the container to enable a persistent cache or share global configuration:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
--volume $COMPOSER_HOME:/tmp \
%%IMAGE%% install
@ -34,9 +34,9 @@ docker run --rm --interactive --tty \
Or if you are following the XDG specification:
```console
COMPOSER_HOME=$HOME/.config/composer \
COMPOSER_CACHE_DIR=$HOME/.cache/composer \
docker run --rm --interactive --tty \
$ COMPOSER_HOME=$HOME/.config/composer \
COMPOSER_CACHE_DIR=$HOME/.cache/composer \
docker run --rm --interactive --tty \
--env COMPOSER_HOME \
--env COMPOSER_CACHE_DIR \
--volume $COMPOSER_HOME:$COMPOSER_HOME \
@ -50,7 +50,7 @@ docker run --rm --interactive --tty \
By default, Composer runs as root inside the container. This can lead to permission issues on your host filesystem. You can work around this by running the container with a different user:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
--user $(id -u):$(id -g) \
%%IMAGE%% install
@ -61,7 +61,7 @@ docker run --rm --interactive --tty \
When you need to access private repositories, you will either need to share your configured credentials, or mount your `ssh-agent` socket inside the running container:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
--volume $SSH_AUTH_SOCK:/ssh-auth.sock \
--env SSH_AUTH_SOCK=/ssh-auth.sock \
@ -73,7 +73,7 @@ docker run --rm --interactive --tty \
When combining the use of private repositories with running Composer as another user, you might run into non-existent user errors (thrown by ssh). To work around this, simply mount the host passwd and group files (read-only) into the container:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
--volume $SSH_AUTH_SOCK:/ssh-auth.sock \
--volume /etc/passwd:/etc/passwd:ro \
@ -91,13 +91,13 @@ Our image is aimed at quickly running Composer without the need for having a PHP
Suggestions:
* use [`--ignore-platform-reqs`](https://getcomposer.org/doc/03-cli.md#install-i):
- use [`--ignore-platform-reqs`](https://getcomposer.org/doc/03-cli.md#install-i):
```console
composer install --ignore-platform-reqs
$ composer install --ignore-platform-reqs
```
* specify the target [platform](https://getcomposer.org/doc/06-config.md#platform) in your `composer.json`:
- specify the target [platform](https://getcomposer.org/doc/06-config.md#platform) in your `composer.json`:
```json
{
@ -118,7 +118,7 @@ Suggestions:
- pass the `--ignore-platform-reqs` and / or `--no-scripts` flags to `install` or `update`:
```console
docker run --rm --interactive --tty \
$ docker run --rm --interactive --tty \
--volume $PWD:/app \
%%IMAGE%% install --ignore-platform-reqs --no-scripts
```