Skip to content

Update build image from debian 11 to 12 - #7755

Draft
MichelLosier wants to merge 1 commit into
elastic:mainfrom
MichelLosier:fix-build-usage-debian-11-to-12
Draft

Update build image from debian 11 to 12#7755
MichelLosier wants to merge 1 commit into
elastic:mainfrom
MichelLosier:fix-build-usage-debian-11-to-12

Conversation

@MichelLosier

@MichelLosier MichelLosier commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

What is the problem this PR solves?

Now that Debian11 is EOL, builds on main can fail when using the Debian11 image.

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

This updates fleet-server-builder to use Debian12

How to test this PR locally

Design Checklist

  • I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
  • I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
  • I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool

Related issues

@MichelLosier
MichelLosier requested a review from a team as a code owner September 2, 2026 16:52
@MichelLosier
MichelLosier requested review from blakerouse and samuelvl and a lite review from Copilot and removed request for Copilot September 2, 2026 16:52
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@mergify

mergify Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This pull request does not have a backport label. Could you fix it @MichelLosier? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant