From c591f8327fddc68931a65e760da4cff37a75a74a Mon Sep 17 00:00:00 2001 From: bilby91 <2201079+bilby91@users.noreply.github.com> Date: Mon, 31 Aug 2026 15:26:51 +0000 Subject: [PATCH] chore(test): drop the stale podman mention from the capability comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment above the CapAdd assertion in the compose feature-security test credited capability-name normalization to "Docker/podman". The podman backend is gone (#124) and this test drives Docker only — newEngineWith builds a *docker.Runtime (test/integration/ image_source_test.go:51) — so name just the backend that is actually under test. Comment only; no behavior change. Co-Authored-By: Claude Opus 5 --- test/integration/compose_feature_security_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/integration/compose_feature_security_test.go b/test/integration/compose_feature_security_test.go index fa6050d..8ba3c90 100644 --- a/test/integration/compose_feature_security_test.go +++ b/test/integration/compose_feature_security_test.go @@ -129,7 +129,7 @@ func TestComposeSource_FeatureSecurityOptionsApplied(t *testing.T) { if !details.Privileged { t.Error("container is not privileged; feature privileged:true was not applied to the compose service") } - // Docker/podman normalize capability names to the CAP_-prefixed + // Docker normalizes capability names to the CAP_-prefixed // form in inspect output (SYS_ADMIN -> CAP_SYS_ADMIN), so compare // with the prefix stripped. if !hasCapability(details.CapAdd, "SYS_ADMIN") {