Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe use of sha256 hash with Wave #448

Merged
merged 5 commits into from
Apr 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,25 @@ If an access token isn't provided, the following rate limits apply:
- 25 container builds per day
- 250 container pulls per hour

## Known limitation

### Use of sha256 digest in the image name

The Wave does not support the use of sha256 digest in the image name, e.g. `ubuntu@sha256:3235...ce8f`, when using
the augmentation process to extend container images.

In order to reference a container via sha256 digest in the image name with Wave you will need to *freeze* image mode
that will force the creation of a new container image using the container you have specified as base image.

In your pipeline configuration, ensure that you specify the following settings:

```groovy
wave.enabled = true
wave.freeze = true
wave.strategy = ['dockerfile']
wave.build.repository = 'docker.io/<user>/<repository>'
```

## Tutorials

### Authenticate private repositories
Expand Down