Skip to content

Commit

Permalink
Update Images Reference
Browse files Browse the repository at this point in the history
Signed-off-by: GitHub <noreply@github.com>
  • Loading branch information
erikaheidi authored Oct 27, 2023
1 parent 008a1fc commit 666cf09
Show file tree
Hide file tree
Showing 69 changed files with 1,353 additions and 75 deletions.
33 changes: 33 additions & 0 deletions content/chainguard/chainguard-images/reference/argo-cli/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: "Image Overview: argo-cli"
linktitle: "argo-cli"
type: "article"
layout: "single"
description: "Overview: argo-cli Chainguard Image"
date: 2022-11-01T11:07:52+02:00
lastmod: 2022-11-01T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
menu:
docs:
parent: "images-reference"
weight: 500
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=true url="/chainguard/chainguard-images/reference/argo-cli/" >}}
{{< tab title="Variants" active=false url="/chainguard/chainguard-images/reference/argo-cli/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-cli/tags_history/" >}}
{{< tab title="Provenance" active=false url="/chainguard/chainguard-images/reference/argo-cli/provenance_info/" >}}
{{</ tabs >}}

Minimal **argo-cli** images with nightly builds.

## Get it!

```
docker pull cgr.dev/chainguard/argo-cli:latest
```

Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "argo-cli Image Variants"
type: "article"
unlisted: true
description: "Detailed information about the public argo-cli Chainguard Image variants"
date: 2023-03-07T11:07:52+02:00
lastmod: 2023-03-07T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
weight: 550
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=false url="/chainguard/chainguard-images/reference/argo-cli/" >}}
{{< tab title="Variants" active=true url="/chainguard/chainguard-images/reference/argo-cli/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-cli/tags_history/" >}}
{{< tab title="Provenance" active=false url="/chainguard/chainguard-images/reference/argo-cli/provenance_info/" >}}
{{</ tabs >}}

This page shows detailed information about all public variants of the Chainguard **argo-cli** Image.

## Variants Compared
The **argo-cli** Chainguard Image currently has 2 public variants:

- `latest-dev`
- `latest`

The table has detailed information about each of these variants.

| | latest-dev | latest |
|--------------|---------------|---------------|
| Default User | `nonroot` | `nonroot` |
| Entrypoint | `argo` | `argo` |
| CMD | not specified | not specified |
| Workdir | not specified | not specified |
| Has apk? | yes | no |
| Has a shell? | yes | no |

Check the [tags history page](/chainguard/chainguard-images/reference/argo-cli/tags_history/) for the full list of available tags.

## Packages Included
The table shows package distribution across variants.

| | latest-dev | latest |
|------------------------------|------------|--------|
| `apk-tools` | X | |
| `argo-workflow-cli` | X | X |
| `argo-workflows` | X | X |
| `argo-workflows-known-hosts` | X | X |
| `bash` | X | |
| `busybox` | X | |
| `ca-certificates-bundle` | X | X |
| `git` | X | |
| `glibc` | X | |
| `glibc-locale-posix` | X | |
| `ld-linux` | X | |
| `libbrotlicommon1` | X | |
| `libbrotlidec1` | X | |
| `libcrypt1` | X | |
| `libcrypto3` | X | |
| `libcurl-openssl4` | X | |
| `libexpat1` | X | |
| `libnghttp2-14` | X | |
| `libpcre2-8-0` | X | |
| `libssl3` | X | |
| `ncurses` | X | |
| `ncurses-terminfo-base` | X | |
| `openssl-config` | X | |
| `wolfi-baselayout` | X | X |
| `zlib` | X | |

Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "Provenance Information for argo-cli Images"
type: "article"
unlisted: true
description: "Provenance information for argo-cli Chainguard Image"
date: 2022-11-01T11:07:52+02:00
lastmod: 2022-11-01T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
weight: 600
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=false url="/chainguard/chainguard-images/reference/argo-cli/" >}}
{{< tab title="Variants" active=false url="/chainguard/chainguard-images/reference/argo-cli/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-cli/tags_history/" >}}
{{< tab title="Provenance" active=true url="/chainguard/chainguard-images/reference/argo-cli/provenance_info/" >}}
{{</ tabs >}}

All Chainguard Images contain verifiable signatures and high-quality SBOMs (software bill of materials), features that enable users to confirm the origin of each image built and have a detailed list of everything that is packed within.

## Verifying Image Signatures
The **argo-cli** Chainguard Images are signed using Sigstore, and you can check the included signatures using `cosign`.

The following command requires [cosign](https://docs.sigstore.dev/cosign/overview/) and [jq](https://stedolan.github.io/jq/) to be installed on your machine. It will pull detailed information about all signatures found for the provided image.

```shell
cosign verify --certificate-oidc-issuer=https://token.actions.githubusercontent.com --certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main cgr.dev/chainguard/argo-cli | jq
```

By default, this command will fetch signatures for the `latest` tag. You can also specify the tag you want to fetch signatures for.

## Downloading and Verifying SBOMs

All Chainguard Images come with a high-quality Software Bill Of Materials (SBOM) attested at build-time. The SBOM can be downloaded using the cosign tool:

```shell
cosign download attestation \
--predicate-type=https://spdx.dev/Document \
cgr.dev/chainguard/argo-cli | jq -r .payload | base64 -d | jq
```
By default, this command will fetch the SBOM assigned to the `latest` tag. You can also specify the tag you want to fetch the SBOM from.

With cosign 2.0+, you can use the `cosign verify-attestation` command to check the signature of an SBOM:

```shell
cosign verify-attestation \
--type https://spdx.dev/Document \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main \
--platform=linux/amd64 \
cgr.dev/chainguard/argo-cli
```

And you should get output that verifies the SBOM signature in cosign's transparency log:

```
Verification for cgr.dev/chainguard/argo-cli --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
Certificate subject: https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main
Certificate issuer URL: https://token.actions.githubusercontent.com
GitHub Workflow Trigger: schedule
GitHub Workflow SHA: da283c26829d46c2d2883de5ff98bee672428696
GitHub Workflow Name: .github/workflows/release.yaml
GitHub Workflow Trigger chainguard-images/images
GitHub Workflow Ref: refs/heads/main
...
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
title: "argo-cli Image Tags History"
type: "article"
unlisted: true
description: "Image Tags and History for the argo-cli Chainguard Image"
date: 2023-06-22T11:07:52+02:00
lastmod: 2023-06-22T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
weight: 700
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=false url="/chainguard/chainguard-images/reference/argo-cli/" >}}
{{< tab title="Variants" active=false url="/chainguard/chainguard-images/reference/argo-cli/image_specs/" >}}
{{< tab title="Tags History" active=true url="/chainguard/chainguard-images/reference/argo-cli/tags_history/" >}}
{{< tab title="Provenance" active=false url="/chainguard/chainguard-images/reference/argo-cli/provenance_info/" >}}
{{</ tabs >}}

The following table contains the most recent tags and digests that can be used to pin your Dockerfile to a specific build of this image. Check our guide on [Using the Tag History API](/chainguard/chainguard-images/using-the-tag-history-api/) for information on how to fetch all tags from an image and how to pin your Dockerfile to a specific digest.

Please note that digests and timestamps only change when there is a change to the image, even though images are rebuilt every night. The "Last Changed" column indicates when the image was last modified, and doesn't always reflect the latest build timestamp. For more information about how our reproducible builds work, please refer to [this blog post](https://www.chainguard.dev/unchained/reproducing-chainguards-reproducible-image-builds).

| Tag (s) | Last Changed | Digest |
|---------------|--------------|---------------------------------------------------------------------------|
| `latest-dev` | October 26th | `sha256:96bf37eeec5f6dacc15de2f6c2a8e0c2c9530e02e0091a37618d5bf79d98d81c` |
| `latest` | October 26th | `sha256:db7956d7cfcf3bf48d4ddeff9819ca904c6ba41d4bde41de3d628112065e9f5e` |

33 changes: 33 additions & 0 deletions content/chainguard/chainguard-images/reference/argo-exec/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: "Image Overview: argo-exec"
linktitle: "argo-exec"
type: "article"
layout: "single"
description: "Overview: argo-exec Chainguard Image"
date: 2022-11-01T11:07:52+02:00
lastmod: 2022-11-01T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
menu:
docs:
parent: "images-reference"
weight: 500
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=true url="/chainguard/chainguard-images/reference/argo-exec/" >}}
{{< tab title="Variants" active=false url="/chainguard/chainguard-images/reference/argo-exec/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-exec/tags_history/" >}}
{{< tab title="Provenance" active=false url="/chainguard/chainguard-images/reference/argo-exec/provenance_info/" >}}
{{</ tabs >}}

Minimal **argo-exec** images with nightly builds.

## Get it!

```
docker pull cgr.dev/chainguard/argo-exec:latest
```

Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "argo-exec Image Variants"
type: "article"
unlisted: true
description: "Detailed information about the public argo-exec Chainguard Image variants"
date: 2023-03-07T11:07:52+02:00
lastmod: 2023-03-07T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
weight: 550
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=false url="/chainguard/chainguard-images/reference/argo-exec/" >}}
{{< tab title="Variants" active=true url="/chainguard/chainguard-images/reference/argo-exec/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-exec/tags_history/" >}}
{{< tab title="Provenance" active=false url="/chainguard/chainguard-images/reference/argo-exec/provenance_info/" >}}
{{</ tabs >}}

This page shows detailed information about all public variants of the Chainguard **argo-exec** Image.

## Variants Compared
The **argo-exec** Chainguard Image currently has 2 public variants:

- `latest-dev`
- `latest`

The table has detailed information about each of these variants.

| | latest-dev | latest |
|--------------|---------------|---------------|
| Default User | `nonroot` | `nonroot` |
| Entrypoint | `argoexec` | `argoexec` |
| CMD | not specified | not specified |
| Workdir | not specified | not specified |
| Has apk? | yes | no |
| Has a shell? | yes | no |

Check the [tags history page](/chainguard/chainguard-images/reference/argo-exec/tags_history/) for the full list of available tags.

## Packages Included
The table shows package distribution across variants.

| | latest-dev | latest |
|---------------------------------|------------|--------|
| `apk-tools` | X | |
| `argo-workflow-executor` | X | X |
| `argo-workflow-executor-compat` | X | X |
| `argo-workflows-known-hosts` | X | X |
| `bash` | X | |
| `busybox` | X | |
| `ca-certificates-bundle` | X | X |
| `git` | X | |
| `glibc` | X | |
| `glibc-locale-posix` | X | |
| `ld-linux` | X | |
| `libbrotlicommon1` | X | |
| `libbrotlidec1` | X | |
| `libcrypt1` | X | |
| `libcrypto3` | X | |
| `libcurl-openssl4` | X | |
| `libexpat1` | X | |
| `libnghttp2-14` | X | |
| `libpcre2-8-0` | X | |
| `libssl3` | X | |
| `ncurses` | X | |
| `ncurses-terminfo-base` | X | |
| `openssl-config` | X | |
| `wolfi-baselayout` | X | X |
| `zlib` | X | |

Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "Provenance Information for argo-exec Images"
type: "article"
unlisted: true
description: "Provenance information for argo-exec Chainguard Image"
date: 2022-11-01T11:07:52+02:00
lastmod: 2022-11-01T11:07:52+02:00
draft: false
tags: ["Reference", "Chainguard Images", "Product"]
images: []
weight: 600
toc: true
---

{{< tabs >}}
{{< tab title="Overview" active=false url="/chainguard/chainguard-images/reference/argo-exec/" >}}
{{< tab title="Variants" active=false url="/chainguard/chainguard-images/reference/argo-exec/image_specs/" >}}
{{< tab title="Tags History" active=false url="/chainguard/chainguard-images/reference/argo-exec/tags_history/" >}}
{{< tab title="Provenance" active=true url="/chainguard/chainguard-images/reference/argo-exec/provenance_info/" >}}
{{</ tabs >}}

All Chainguard Images contain verifiable signatures and high-quality SBOMs (software bill of materials), features that enable users to confirm the origin of each image built and have a detailed list of everything that is packed within.

## Verifying Image Signatures
The **argo-exec** Chainguard Images are signed using Sigstore, and you can check the included signatures using `cosign`.

The following command requires [cosign](https://docs.sigstore.dev/cosign/overview/) and [jq](https://stedolan.github.io/jq/) to be installed on your machine. It will pull detailed information about all signatures found for the provided image.

```shell
cosign verify --certificate-oidc-issuer=https://token.actions.githubusercontent.com --certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main cgr.dev/chainguard/argo-exec | jq
```

By default, this command will fetch signatures for the `latest` tag. You can also specify the tag you want to fetch signatures for.

## Downloading and Verifying SBOMs

All Chainguard Images come with a high-quality Software Bill Of Materials (SBOM) attested at build-time. The SBOM can be downloaded using the cosign tool:

```shell
cosign download attestation \
--predicate-type=https://spdx.dev/Document \
cgr.dev/chainguard/argo-exec | jq -r .payload | base64 -d | jq
```
By default, this command will fetch the SBOM assigned to the `latest` tag. You can also specify the tag you want to fetch the SBOM from.

With cosign 2.0+, you can use the `cosign verify-attestation` command to check the signature of an SBOM:

```shell
cosign verify-attestation \
--type https://spdx.dev/Document \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main \
--platform=linux/amd64 \
cgr.dev/chainguard/argo-exec
```

And you should get output that verifies the SBOM signature in cosign's transparency log:

```
Verification for cgr.dev/chainguard/argo-exec --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
Certificate subject: https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main
Certificate issuer URL: https://token.actions.githubusercontent.com
GitHub Workflow Trigger: schedule
GitHub Workflow SHA: da283c26829d46c2d2883de5ff98bee672428696
GitHub Workflow Name: .github/workflows/release.yaml
GitHub Workflow Trigger chainguard-images/images
GitHub Workflow Ref: refs/heads/main
...
```
Loading

0 comments on commit 666cf09

Please sign in to comment.