build(gha): move export to docker section to dedicated page

Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
CrazyMax 2023-02-23 01:15:43 +01:00
parent c3b01c8155
commit 989141fc21
No known key found for this signature in database
GPG Key ID: 3248E46B6BB8C7F7
3 changed files with 42 additions and 36 deletions

View File

@ -1619,6 +1619,8 @@ manuals:
title: Manage tags and labels title: Manage tags and labels
- path: /build/ci/github-actions/cache/ - path: /build/ci/github-actions/cache/
title: Cache management title: Cache management
- path: /build/ci/github-actions/export-docker/
title: Export to Docker
- path: /build/ci/github-actions/examples/ - path: /build/ci/github-actions/examples/
title: Examples title: Examples
- sectiontitle: Bake - sectiontitle: Bake

View File

@ -7,42 +7,6 @@ keywords: ci, github actions, gha, examples
This page showcases different examples of how you can customize and use the This page showcases different examples of how you can customize and use the
Docker GitHub Actions in your CI pipelines. Docker GitHub Actions in your CI pipelines.
## Export image to Docker
You may want your build result to be available in the Docker client through
`docker images` to be able to use it in another step of your workflow:
```yaml
name: ci
on:
push:
branches:
- "main"
jobs:
docker:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v3
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
-
name: Build
uses: docker/build-push-action@v4
with:
context: .
load: true
tags: myimage:latest
-
name: Inspect
run: |
docker image inspect myimage:latest
```
## Test your image before pushing it ## Test your image before pushing it
In some cases, you might want to validate that the image works as expected In some cases, you might want to validate that the image works as expected

View File

@ -0,0 +1,40 @@
---
title: Export to Docker with GitHub Actions
keywords: ci, github actions, gha, buildkit, buildx, docker
---
You may want your build result to be available in the Docker client through
`docker images` to be able to use it in another step of your workflow:
{% raw %}
```yaml
name: ci
on:
push:
branches:
- "main"
jobs:
docker:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v3
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
-
name: Build
uses: docker/build-push-action@v4
with:
context: .
load: true
tags: myimage:latest
-
name: Inspect
run: |
docker image inspect myimage:latest
```
{% endraw %}