From fe4ba3c5d822f72e3bd44c18fcfa91f64e4da92e Mon Sep 17 00:00:00 2001 From: Johannes Kastl ATVANTAGE <157097848+kastl-ars@users.noreply.github.com> Date: Tue, 4 Aug 2026 14:26:15 +0200 Subject: [PATCH] [documentation] make intro example actually usable (#6953) Signed-off-by: Johannes Kastl --- docs/docs/20-usage/10-intro.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/20-usage/10-intro.md b/docs/docs/20-usage/10-intro.md index affe61b47..4a2f2d250 100644 --- a/docs/docs/20-usage/10-intro.md +++ b/docs/docs/20-usage/10-intro.md @@ -25,12 +25,12 @@ steps: image: debian commands: - echo "This is the build step" - - echo "binary-data-123" > executable + - echo "some-data" > some-file.txt - name: a-test-step - image: golang:1.16 + image: alpine commands: - echo "Testing ..." - - ./executable + - cat some-file.txt ``` **So what did we do here?** @@ -51,9 +51,9 @@ steps: The steps are executed in the order they are defined, so `build` will be executed first and then `a-test-step`. -In the `build` step we use the `debian` image and build a "binary file" called `executable`. +In the `build` step we use the `debian` image and create a file called `some-file.txt`. -In the `a-test-step` we use the `golang:1.16` image and run the `executable` file to test it. +In the `a-test-step` we use the `alpine` image and output the `some-file.txt` file contents. You can use any image from registries like the [Docker Hub](https://hub.docker.com/search?type=image) you have access to: