You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lando-service.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Generally you will want to use a more specific service like `type: php` but this
13
13
* Using Docker Compose config from other projects
14
14
* Need a service not currently provided by Lando itself
15
15
16
-
It implements a super-set of the [Docker Compose Version 3 Spec](https://docs.docker.com/compose/compose-file/compose-file-v3/) and _usually_ requires some [slight tweaks](#caveats) of existing Docker Compose configuration to work correctly.
16
+
It implements a super-set of the [Docker Compose Version 3 Spec](https://docs.docker.com/compose/compose-file/) and _usually_ requires some [slight tweaks](#caveats) of existing Docker Compose configuration to work correctly.
# note that these are only available if you invoke the service directly
32
32
services: {}
33
33
networks: {}
@@ -51,7 +51,7 @@ services:
51
51
52
52
## Services, Networks, Volumes
53
53
54
-
These three: `services,` `networks` and `volumes` map directly to the [Docker Compose Version 3 Spec](https://docs.docker.com/compose/compose-file/compose-file-v3/) which means that the below is a valid Landofile:
54
+
These three: `services,` `networks` and `volumes` map directly to the [Docker Compose Version 3 Spec](https://docs.docker.com/compose/compose-file/) which means that the below is a valid Landofile:
55
55
56
56
**Landofile**
57
57
```yaml
@@ -351,7 +351,7 @@ Since [Lando 3.14.0](https://github.com/lando/lando/releases/tag/v3.14.0) servic
351
351
352
352
## Overrides
353
353
354
-
Lando services are just an abstraction layer on top of the [Docker compose v3 file format](https://docs.docker.com/compose/compose-file/compose-file-v3/). What this means is that behind the scenes your Landofile is being translated into a *SHLOAD* of *SUPERNASTY* looking `docker-compose` files which are then being used to power your app.
354
+
Lando services are just an abstraction layer on top of the [Docker compose v3 file format](https://docs.docker.com/compose/compose-file/). What this means is that behind the scenes your Landofile is being translated into a *SHLOAD* of *SUPERNASTY* looking `docker-compose` files which are then being used to power your app.
355
355
356
356
We give you access to the Docker Compose layer with the `overrides` key.
Copy file name to clipboardExpand all lines: docs/services/l337.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The `l337` service is the lowest level `api: 4` service and it implements **L**a
14
14
15
15
In high level terms it combines _service orchestration_ and _image specification_ into a single file format.
16
16
17
-
Specifically, it is a light superset around the [Docker Compose Version 3](https://docs.docker.com/compose/compose-file/compose-file-v3/) format that also uses the [Dockerfile](https://docs.docker.com/engine/reference/builder/) specification.
17
+
Specifically, it is a light superset around the [Docker Compose Version 3](https://docs.docker.com/compose/compose-file/) format that also uses the [Dockerfile](https://docs.docker.com/engine/reference/builder/) specification.
18
18
19
19
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".
20
20
@@ -103,7 +103,7 @@ services:
103
103
image:
104
104
imagefile: "nginx:1.21"
105
105
tag: "pirog/nginx:1.21"
106
-
buildx: true
106
+
buildkit: true
107
107
ssh: false
108
108
args:
109
109
vibe: rising
@@ -194,7 +194,7 @@ services:
194
194
195
195
Array formatted `key=value` pairs are trimmed in both `key` and `value`. Args with no `value` are ignored as in `something` above.
196
196
197
-
### Buildx
197
+
### Buildkit
198
198
199
199
If _for some reason_ you prefer to use the old pre-BuildKit image builder you can toggle this to `false`.
200
200
@@ -205,13 +205,13 @@ services:
205
205
# use the legacy builder
206
206
example-1:
207
207
api: 4
208
-
buildx: false
208
+
buildkit: false
209
209
type: l337
210
210
image:
211
211
imagefile: nginx:1.21
212
212
```
213
213
214
-
Note that if you do `buildx: false` some image build features, specifically those in [Dockerfile 1.1.0+](https://docs.docker.com/build/dockerfile/release-notes/#110) and the [ssh](#ssh) features of this service, may not be available.
214
+
Note that if you do `buildkit: false` some image build features, specifically those in [Dockerfile 1.1.0+](https://docs.docker.com/build/dockerfile/release-notes/#110) and the [ssh](#ssh) features of this service, may not be available. You can also use `buildx` as an alias for `buildkit`. If you use both it will evaluate to `true` if either is `true`. Really just don't use both ;)!
215
215
216
216
You probably should just ignore this setting unless you have a well understood reason to do otherwise.
217
217
@@ -430,7 +430,7 @@ lando rebuild
430
430
Here are some additional notes on this feature:
431
431
432
432
* Passphrase protected keys can be used but only if added to your host `ssh-agent`_before_ image build
433
-
* This feature is not available if you set `buildx: false`
433
+
* This feature is not available if you set `buildkit: false`
434
434
* The keys/agent are only available when explicitly mounted in a `RUN` instruction they **DO NOT** end up in the resulting image
0 commit comments