Commit dc3411d3 authored by Boris Kuznetsov's avatar Boris Kuznetsov

The project doesn't use docker-compose at all

parent b368a45c
...@@ -105,7 +105,6 @@ not without its own challenges: ...@@ -105,7 +105,6 @@ not without its own challenges:
- **The `docker-compose` command**: This command is not available in this configuration by default. - **The `docker-compose` command**: This command is not available in this configuration by default.
To use `docker-compose` in your job scripts, follow the `docker-compose` To use `docker-compose` in your job scripts, follow the `docker-compose`
[installation instructions](https://docs.docker.com/compose/install/). [installation instructions](https://docs.docker.com/compose/install/).
You can view a sample project that uses this approach here: <https://gitlab.com/gitlab-examples/docker>.
- **Cache**: Each job runs in a new environment. Concurrent jobs work fine, - **Cache**: Each job runs in a new environment. Concurrent jobs work fine,
because every build gets its own instance of Docker engine and they don't conflict with each other. because every build gets its own instance of Docker engine and they don't conflict with each other.
However, jobs can be slower because there's no caching of layers. However, jobs can be slower because there's no caching of layers.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment