Skip to content

chore(backend): bump Dockerfile.jvm OpenJDK 21 UBI base image tag 1.20 → 1.24 #144

Description

@hugomelendez

Problem / need

The backend container image pins outdated Red Hat UBI9 OpenJDK 21 base tags (1.21) in backend/Dockerfile.jvm. Quarkus 3.x and the current RH OpenJDK container stream use tag 1.24. Staying on 1.21 misses platform updates and diverges from Quarkus defaults.

Proposed solution

Update both FROM lines in backend/Dockerfile.jvm:

  • registry.access.redhat.com/ubi9/openjdk-21:1.21 → registry.access.redhat.com/ubi9/openjdk-21:1.24
  • registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21 → registry.access.redhat.com/ubi9/openjdk-21-runtime:1.24

Verify:

  • CI Build and push to Quay succeeds on the PR
  • Optional local: podman build -f backend/Dockerfile.jvm backend/
  • Backend starts and serves API (smoke via compose or Helm)

Suggested milestone

Backlog

Impacted repos

  • gateforge

Activity

  1. changed the title [-]chore(backend): bump Dockerfile.jvm OpenJDK UBI base image tag 1.20 → 1.24[/-] [+]chore(backend): bump Dockerfile.jvm OpenJDK 21 UBI base image tag 1.20 → 1.24[/+] on Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions