Skip to content

[8.19](backport #43839) docker: use the official Red Hat images #43967

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 8.19
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 16, 2025

Proposed commit message

use the official Red Hat images

Release engineering team is cleaning up legacy UBI images from Elastic's internal Docker registry. Please use the official Red Hat images instead. The following list of images is planned to be removed on May 16th:

Checklist

  • My code follows the style guidelines of this project
  • 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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs


This is an automatic backport of pull request #43839 done by [Mergify](https://mergify.com).

(cherry picked from commit afa6ac6)

# Conflicts:
#	dev-tools/packaging/packages.yml
@mergify mergify bot requested a review from a team as a code owner April 16, 2025 21:04
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Apr 16, 2025
@mergify mergify bot requested review from mauri870 and VihasMakwana and removed request for a team April 16, 2025 21:04
@mergify mergify bot assigned v1v Apr 16, 2025
Copy link
Contributor Author

mergify bot commented Apr 16, 2025

Cherry-pick of afa6ac6 has failed:

On branch mergify/bp/8.19/pr-43839
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit afa6ac640.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   dev-tools/packaging/packages.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 16, 2025
@mergify mergify bot mentioned this pull request Apr 16, 2025
6 tasks
@github-actions github-actions bot added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Apr 16, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 16, 2025
@v1v v1v removed the conflicts There is a conflict in the backported pull request label Apr 16, 2025
@v1v
Copy link
Member

v1v commented Apr 16, 2025

Conflicts were caused by #42150

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants