Skip to content

dhi: update vex get #23367

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 8, 2025
Merged

dhi: update vex get #23367

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions content/manuals/dhi/core-concepts/cves.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,19 +153,18 @@ manual configuration needed.
To manually retrieve the VEX attestation for tools that support it:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
<your-namespace>/dhi-<image>:<tag> --platform <platform> > vex.json
$ docker scout vex get <your-namespace>/dhi-<image>:<tag> --output vex.json
```

> [!NOTE]
>
> The `docker scout vex get` command requires [Docker Scout
> CLI](https://github.com/docker/scout-cli/) version 1.18.3 or later.

For example:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
docs/dhi-python:3.13 --platform linux/amd64 > vex.json
$ docker scout vex get docs/dhi-python:3.13 --output vex.json
```

This creates a `vex.json` file containing the VEX statements for the specified
Expand Down
15 changes: 7 additions & 8 deletions content/manuals/dhi/core-concepts/vex.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,19 +63,18 @@ manual configuration is needed.
To manually retrieve the VEX attestation for tools that support it:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
<your-namespace>/dhi-<image>:<tag> --platform <platform> > vex.json
$ docker scout vex get <your-namespace>/dhi-<image>:<tag> --output vex.json
```

> [!NOTE]
>
> The `docker scout vex get` command requires [Docker Scout
> CLI](https://github.com/docker/scout-cli/) version 1.18.3 or later.

For example:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
docs/dhi-python:3.13 --platform linux/amd64 > vex.json
$ docker scout vex get docs/dhi-python:3.13 --output vex.json
```

This creates a `vex.json` file containing the VEX statements for the specified
Expand Down
20 changes: 10 additions & 10 deletions content/manuals/dhi/how-to/scan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,26 +191,26 @@ runtime behavior.
When using Docker Scout, these VEX statements are automatically applied and no
manual configuration needed.

To manually create a JSON file VEX attestation for tools that support it:
To manually create a JSON file of VEX attestations for tools that support it:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
<your-namespace>/dhi-<image>:<tag> --platform <platform> > vex.json
$ docker scout vex get <your-namespace>/dhi-<image>:<tag> --output vex.json
```

> [!NOTE]
>
> The `docker scout vex get` command requires [Docker Scout
> CLI](https://github.com/docker/scout-cli/) version 1.18.3 or later.

For example:

```console
$ docker scout attest get \
--predicate-type https://openvex.dev/ns/v0.2.0 \
--predicate \
docs/dhi-python:3.13 --platform linux/amd64 > vex.json
$ docker scout vex get docs/dhi-python:3.13 --output vex.json
```

This creates a `vex.json` file containing the VEX statements for the specified
image. You can then use this file with tools that support VEX to filter out known non-exploitable CVEs.
image. You can then use this file with tools that support VEX to filter out
known non-exploitable CVEs.

For example, with Grype and Trivy, you can use the `--vex` flag to apply the VEX
statements during the scan:
Expand Down