Repository navigation
build(deps): bump the docker group in /packaging/docker with 2 updates - #22408
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the docker group in /packaging/docker with 2 updates: ubuntu and ubi10-micro. Updates `ubuntu` from `68ee220` to `fe81560` Updates `ubi10-micro` from `1c105e5` to `8488f5e` --- updated-dependencies: - dependency-name: ubuntu dependency-version: '24.04' dependency-type: direct:production dependency-group: docker - dependency-name: ubi10-micro dependency-version: latest dependency-type: direct:production dependency-group: docker ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
🤖 GitHub commentsJust comment with:
|
There was a problem hiding this comment.
🔵 Needs a closer look
The referenced image manifests and contents are unavailable locally, so CI must confirm digest resolution, required architecture support, and container-build compatibility.
No open issues 🎉
What changed in this PR
Updates the pinned base-image digests used to package APM Server’s Ubuntu and UBI Docker images, without changing image tags or build logic.
Changes:
- Bumps Ubuntu 24.04 from digest
68ee220tofe81560. - Bumps UBI 10 Micro from digest
1c105e5to8488f5e.
| File | Description |
|---|---|
| packaging/docker/Dockerfile | Updates the Ubuntu and UBI base-image digest pins. |
Review effort: Balanced
Dependency Update AnalysisSummary: This PR updates two Docker base-image digests in ubuntu 24.04 digest
|
| Check | Result |
|---|---|
| Breaking changes | ✅ None found |
| Testable in PR | ✅ Yes (.github/workflows/ci.yml runs on pull_request, including test-package → make package-snapshot) |
Changelog highlights (`68ee220` → `fe81560`)
Digest-only image pin bump. Upstream Ubuntu release-note/changelog body for this exact digest was not available from local repo metadata; local Dependabot metadata confirms only the digest update under ubuntu:24.04.
Usage in this repository
packaging/docker/Dockerfile:5definesbase-ubuntufromubuntu:24.04@sha256:....packaging.mk:49builds Docker artifacts frompackaging/docker/Dockerfile.packaging.mk:53/ build targets consume this base stage when building release/snapshot images.Tiltfile:45uses the same Dockerfile for local image builds.
Compatibility assessment
This is a same-tag digest refresh, so Docker build inputs and stage names are unchanged. Repository usage depends on Dockerfile stages/paths, not OS-level APIs from the base image. No consumed interfaces changed in-repo; residual risk is runtime package drift inside the new base image digest.
ubi10-micro digest 1c105e5 → 8488f5e
Ecosystem: CI / container / snapshot image pins
| Check | Result |
|---|---|
| Breaking changes | ✅ None found |
| Testable in PR | ✅ Yes (.github/workflows/ci.yml runs on pull_request, including packaging jobs) |
Changelog highlights (`1c105e5` → `8488f5e`)
Digest-only image pin bump for registry.access.redhat.com/ubi10-micro:latest. Detailed upstream changelog text for this exact digest was not present in local metadata; local Dependabot metadata confirms the digest transition only.
Usage in this repository
packaging/docker/Dockerfile:6definesbase-ubifromubi10-micro:latest@sha256:....packaging.mk:51selectsBASE_STAGE=base-ubifor UBI image builds.- Packaging/publish flow in
packaging.mkand CI packaging jobs consume this stage for UBI artifacts.
Compatibility assessment
The Dockerfile stage contract (base-ubi) and build args remain unchanged; only the immutable digest changed. No repo code/API integration points depend on changed interfaces here. Risk is mainly OS package/content changes within the new digest, bounded by PR packaging/test workflow execution.
Labels Applied
oblt-aw/ai/merge-ready— Applied (risk low-to-moderate, no breaking usage changes found, and PR-context testability is present).
What is this? | From workflow: Observability Agentic Workflow — Pull Request
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Automerge skippedAutomerge skipped this pull request because the To allow automerge for this kind of update, enable the matching collection under Automerge on the Control Plane Dashboard (the See Opt in or opt out for how to enable or disable Automerge collections on the Control Plane Dashboard. Collections currently enabled for automerge: Changed files considered:
|
💚 Build Succeeded
|
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps the docker group in /packaging/docker with 2 updates: ubuntu and ubi10-micro.
Updates
ubuntufrom68ee220tofe81560Updates
ubi10-microfrom1c105e5to8488f5eDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions