Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion default.env
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ BASE_URL=http://localhost:7007

# Default plugin catalog index image
# Requires RHDH 1.9+ to be handled.
CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.9
CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.10

# Path in the install-dynamic-plugins container where the extensions catalog entities should be extracted to, from the catalog index image
# Requires RHDH 1.9+ to be handled
Expand Down
14 changes: 7 additions & 7 deletions docs/rhdh-local-guide/container-image-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This allows RHDH-local to pull OCI artifacts from registries like registry.redha

## Changing the container image

By default, the [compose.yaml](https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml) points to the latest, stable **community build of RHDH** at [quay.io/rhdh-community/rhdh:1.7](https://quay.io/rhdh-community/rhdh:1.7), which includes both `linux-amd64` and `linux-arm64` images.
By default, the [compose.yaml](https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml) points to the latest, stable **community build of RHDH** at [quay.io/rhdh-community/rhdh:1.9](https://quay.io/rhdh-community/rhdh:1.9), which includes both `linux-amd64` and `linux-arm64` images.

Community builds are [built with Github Actions](https://github.com/redhat-developer/rhdh/blob/main/.github/workflows/next-build-image.yaml#L46-L47) and [docker buildx](https://github.com/redhat-developer/rhdh/blob/main/.github/actions/docker-build/action.yaml), using the same sources as the commercially supported builds.

Expand All @@ -26,10 +26,10 @@ Looking for the bleeding edge? To use the most recent nightly community build of
RHDH_IMAGE=quay.io/rhdh-community/rhdh:next
```

Or, for builds from a given `release-1.y` branch (for example, 1.8), set the variable as follows.
Or, for builds from a given `release-1.y` branch (for example, 1.10), set the variable as follows.

```sh
RHDH_IMAGE=quay.io/rhdh-community/rhdh:next-1.8
RHDH_IMAGE=quay.io/rhdh-community/rhdh:next-1.10
```

### Using unsupported pre-release CI builds
Expand All @@ -38,20 +38,20 @@ Continuous Integration (CI) builds on from [quay.io/rhdh/rhdh-hub-rhel9](https:/

NOTE: Only `linux-amd64` builds are currently commercially supported.

To use the most recent nightly CI build of RHDH 1.y (for example, 1.8), set the variable as follows.
To use the most recent nightly CI build of RHDH 1.y (for example, 1.10), set the variable as follows.

```sh
RHDH_IMAGE=quay.io/rhdh/rhdh-hub-rhel9:1.8
RHDH_IMAGE=quay.io/rhdh/rhdh-hub-rhel9:1.10
```

### Using commercially supported official images

To use the [official release of RHDH](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?gs&q=developer%20hub) 1.y (for example, 1.8), which includes only `linux-amd64`, set the variable as follows.
To use the [official release of RHDH](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?gs&q=developer%20hub) 1.y (for example, 1.9), which includes only `linux-amd64`, set the variable as follows.

NOTE: Using official builds also [requires authentication with the registry](https://access.redhat.com/articles/RegistryAuthentication). See also the section below `Configuring registry credentials` to make this authentication pervasive.

```sh
RHDH_IMAGE=registry.redhat.io/rhdh/rhdh-hub-rhel9:1.8.3
RHDH_IMAGE=registry.redhat.io/rhdh/rhdh-hub-rhel9:1.9
```

#### Using image digests
Expand Down