Skip to content

debian bookworm EOL 10 June 2026 #9310

Description

@DWS-guy

the base docker image debian:bookwom-slim will become EOL this June and should be updated to stay with a currently supported OS.

12 Bookworm 2023-06-10 2026-06-10 2028-06-30 2033-06-30 Current oldstable release

12 Bookworm 2023-06-10 2026-06-10 2028-06-30 2033-06-30 Current oldstable release

Activity

  1. thc202 commented on Apr 24, 2026

    @thc202
    Member

    and two years of Long Term Support (LTS), until June 30th, 2028. the base image will be updated in the next ZAP release (as per nightly and weekly).

  2. added this to the 2.18.0 milestone on Apr 24, 2026
  3. DWS-guy commented on Apr 24, 2026

    @DWS-guy
    Author

    The CVE for mesa (CVE-2026-40393 - mesa) is a roadblock for my team as of now. debian:sid has a patched version.

  4. chetannyadavv commented on May 25, 2026

    @chetannyadavv

    Hi! I'd like to work on this.

    My plan:

    • Bump both Dockerfile stages from debian:bookworm-slim to debian:trixie-slim
    • Upgrade from openjdk-17-jdk to openjdk-21-jdk since openjdk-17
      is not available in Trixie's default repos
    • Update JAVA_HOME path accordingly
    • Apply to all Dockerfiles in the docker/ directory

    Does this approach sound right, or would you prefer keeping Java 17
    via the Adoptium/Temurin repo instead?

  5. thc202 commented on May 25, 2026

    @thc202
    Member

    The stable image will be changed when preparing the 2.18.0 release.

  6. kingthorin commented on May 25, 2026

    @kingthorin
    Member

    To answer your Java question: The plan is for 2.18.0 to require Java 21.

    https://groups.google.com/g/zaproxy-develop/c/v0jGlz7Envs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions