Fix doc typo

Added a few files to test the affected test.

Signed-off-by: Helder Correia <174525+helderco@users.noreply.github.com>
This commit is contained in:
Helder Correia
2022-03-11 15:11:03 -01:00
parent dcde3c929d
commit 45a1fb19d2
9 changed files with 12 additions and 11 deletions

View File

@@ -7,21 +7,21 @@ displayed_sidebar: europa
You can use Dagger to build container images. Here's a simple example of a [Dockerfile](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/) build:
```cue file=../tests/core-concepts/container-images/plans/with-dockerfile.cue
```cue file=../tests/core-concepts/container-images/simple/with-dockerfile.cue
```
## Building with CUE
`Dockerfile` files are easy to start, but you can also build images entirely in CUE. The following example produces the same image as above:
```cue file=../tests/core-concepts/container-images/plans/build.cue
```cue file=../tests/core-concepts/container-images/simple/build.cue
```
## Automation
Building images in CUE gives you greater flexibility. For example, you can automate building multiple versions of an image, and deploy, all in Dagger:
```cue file=../tests/core-concepts/container-images/plans/template.cue
```cue file=../tests/core-concepts/container-images/template/dagger.cue
```
Now you can deploy all versions:
@@ -40,5 +40,5 @@ dagger do versions 8.0 build
Another common pattern is [multi-stage builds](https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds). This allows you to have heavier build images during the build process, and copy the built artifacts into a cleaner and lighter image to run in production.
```cue file=../tests/core-concepts/container-images/plans/multi-stage.cue
```cue file=../tests/core-concepts/container-images/multi-stage/dagger.cue
```