Skip to content

Commit

Permalink
dockerlinx
Browse files Browse the repository at this point in the history
  • Loading branch information
pirog committed Nov 4, 2024
1 parent cd60065 commit 7a0d276
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/services/l337.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ The `l337` service is the lowest level `api: 4` service and it implements **L**a

In high level terms it combines _service orchestration_ and _image specification_ into a single file format.

Specifically, it is a light superset around the [Docker Compose Version 3](https://docs.docker.com/reference/compose-file/) format that also uses the [Dockerfile](https://docs.docker.com/engine/reference/builder/) specification.
Specifically, it is a light superset around the [Docker Compose Version 3](https://docs.docker.com/reference/compose-file/) format that also uses the [Dockerfile](https://docs.docker.com/reference/dockerfile) specification.

This means that you _should_ be able to paste Docker Compose and/or Dockerfile compatible contents into your Landofile, add `api: 4` to each service and have it "just work".

Expand Down Expand Up @@ -162,7 +162,7 @@ Note that you can also use `dockerfile` instead of `imagefile` if you prefer tha

### Build Args

You can pass in [build args](https://docs.docker.com/build/guide/build-args/) that are then used by your `image` instructions. Both `array` and `object` notation is permissible but `object` is probably better.
You can pass in [build args](https://docs.docker.com/build/building/variables/) that are then used by your `image` instructions. Both `array` and `object` notation is permissible but `object` is probably better.

**Landofile**
```yaml
Expand Down

0 comments on commit 7a0d276

Please sign in to comment.