Update docker.io/library/ubuntu Docker tag to v26

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker.io/library/ubuntu	final	major	24.04 → 26.04

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dd-prapprover]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule datadog-agent-renovate - 2026-06-16T22:20:51Z
• ✅ CI tests passed - 2026-06-16T22:23:58Z
• ✅ Approved (commit: f4a09b5) - 2026-06-16T22:24:00Z
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: approved - manual merge required (this rule does not auto-merge)

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor cad4ec62:

Results for datadog-agent_7.82.0~devel.git.610.5145964.pipeline.122571934-1_amd64.deb:

No change detected

[dd-prapprover]

This PR has been automatically approved by the DD PR Approver bot.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-16 22:24:16 UTC ℹ️ Start processing command /merge

---

2026-06-16 22:24:22 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-06-17 03:03:03 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-03 11:06:24 UTC ℹ️ Start processing command /merge

---

2026-07-03 11:06:31 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-07-03 15:15:04 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[dd-octo-sts]

Static quality checks

❌ Please find below the results from static quality gates
Comparison made with ancestor cad4ec6
📊 Static Quality Gates Dashboard
🔗 SQG Job

Error

	Quality gate	Change	Size (prev → curr → max)
❌	docker_agent_amd64 (on disk)	+23.34 MiB (2.89% increase, -365.35% of buffer)	807.402 → 830.741 → 813.790
❌	docker_agent_arm64 (on disk)	+20.8 MiB (2.58% increase, -285.98% of buffer)	807.755 → 828.559 → 815.030
❌	docker_agent_jmx_amd64 (on disk)	+24.35 MiB (2.44% increase, -389.49% of buffer)	998.299 → 1022.645 → 1004.550
❌	docker_agent_jmx_arm64 (on disk)	+21.73 MiB (2.20% increase, -293.52% of buffer)	987.305 → 1009.039 → 994.710
❌	docker_cluster_agent_amd64 (on disk)	+28.56 MiB (13.65% increase, -2373.96% of buffer)	209.267 → 237.832 → 210.470
❌	docker_cluster_agent_arm64 (on disk)	+26.28 MiB (11.82% increase, -4439.55% of buffer)	222.388 → 248.669 → 222.980
❌	docker_host_profiler_amd64 (on disk)	+17.01 MiB (5.62% increase, -112.00% of buffer)	302.456 → 319.462 → 317.640

Gate failure full details

Quality gate	Error type	Error message
docker_agent_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_amd64 failed! Disk size 830.7 MB exceeds limit of 813.8 MB by 17.0 MB
docker_agent_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_arm64 failed! Disk size 828.6 MB exceeds limit of 815.0 MB by 13.5 MB
docker_agent_jmx_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_jmx_amd64 failed! Disk size 1022.6 MB exceeds limit of 1004.5 MB by 18.1 MB
docker_agent_jmx_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_jmx_arm64 failed! Disk size 1009.0 MB exceeds limit of 994.7 MB by 14.3 MB
docker_cluster_agent_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_cluster_agent_amd64 failed! Disk size 237.8 MB exceeds limit of 210.5 MB by 27.4 MB
docker_cluster_agent_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_cluster_agent_arm64 failed! Disk size 248.7 MB exceeds limit of 223.0 MB by 25.7 MB
docker_host_profiler_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_host_profiler_amd64 failed! Disk size 319.5 MB exceeds limit of 317.6 MB by 1.8 MB

Static quality gates prevent the PR to merge!
You can check the static quality gates confluence page for guidance. We also have a toolbox page available to list tools useful to debug the size increase.
Please either fix the size violation or request an exception.

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_host_profiler_arm64	+12.55 MiB (4.00% increase, -84.44% of buffer)	314.035 → 326.587 → 328.900

24 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	748.598 MiB
✅	agent_deb_amd64_fips	703.641 MiB
✅	agent_heroku_amd64	307.857 MiB
✅	agent_rpm_amd64	748.581 MiB
✅	agent_rpm_amd64_fips	703.625 MiB
✅	agent_rpm_arm64	723.895 MiB
✅	agent_rpm_arm64_fips	682.671 MiB
✅	agent_suse_amd64	748.581 MiB
✅	agent_suse_amd64_fips	703.625 MiB
✅	agent_suse_arm64	723.895 MiB
✅	agent_suse_arm64_fips	682.671 MiB
✅	docker_cws_instrumentation_amd64	7.447 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.125 MiB
✅	docker_dogstatsd_arm64	37.242 MiB
✅	dogstatsd_deb_amd64	29.864 MiB
✅	dogstatsd_deb_arm64	27.908 MiB
✅	dogstatsd_rpm_amd64	29.864 MiB
✅	dogstatsd_suse_amd64	29.864 MiB
✅	iot_agent_deb_amd64	45.774 MiB
✅	iot_agent_deb_arm64	42.481 MiB
✅	iot_agent_deb_armhf	43.270 MiB
✅	iot_agent_rpm_amd64	45.775 MiB
✅	iot_agent_suse_amd64	45.774 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 4999292f-207f-4e58-a02a-e181d6ece23c

Baseline: f61b031
Comparison: 5145964
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_idle_all_features	memory utilization	+1.00	[+0.96, +1.04]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	+0.46	[+0.39, +0.53]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.44	[+0.39, +0.49]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.36	[+0.33, +0.40]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.21	[+0.12, +0.31]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-0.48	[-1.56, +0.60]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-1.56	[-1.83, -1.30]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	147.19MiB ≤ 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	577.71KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	483.91MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	0.89MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	180.75MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.22MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	342.71 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	383.87MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.86GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	31.27 ≤ 40	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	297.24MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	59.00 ≤ 80	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	277.63MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	29.86 ≤ 40	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	284.58MiB ≤ 320MiB	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Profiling Replicate Execution Failures (ddprof)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	10	Oom killed	Debug Dashboard
quality_gate_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_security_idle	baseline	10	Oom killed	Debug Dashboard
quality_gate_security_idle	comparison	10	Oom killed	Debug Dashboard
quality_gate_security_no_fs_load	baseline	10	Oom killed	Debug Dashboard
quality_gate_security_no_fs_load	comparison	10	Oom killed	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-06 19:19:09 UTC ℹ️ Start processing command /merge

---

2026-07-06 19:19:18 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-07-06 23:22:13 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.