From f8f05611778851680da78873808d9fca84e8db48 Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Tue, 25 Jul 2023 10:14:09 +0200 Subject: [PATCH] Use `UserSpecifiedImage` for seccomp tests The seccomp tests use their own container creation logic, which is why we forgot to add the `UserSpecifiedImage` there as well. This is now fixed. Signed-off-by: Sascha Grunert --- pkg/validate/security_context_linux.go | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/pkg/validate/security_context_linux.go b/pkg/validate/security_context_linux.go index 80f8d79071..a098f1b8a6 100644 --- a/pkg/validate/security_context_linux.go +++ b/pkg/validate/security_context_linux.go @@ -1219,8 +1219,11 @@ func createSeccompContainer(rc internalapi.RuntimeService, containerName := prefix + framework.NewUUID() containerConfig := &runtimeapi.ContainerConfig{ Metadata: framework.BuildContainerMetadata(containerName, framework.DefaultAttempt), - Image: &runtimeapi.ImageSpec{Image: framework.TestContext.TestImageList.DefaultTestContainerImage}, - Command: []string{"sleep", "60"}, + Image: &runtimeapi.ImageSpec{ + Image: framework.TestContext.TestImageList.DefaultTestContainerImage, + UserSpecifiedImage: framework.TestContext.TestImageList.DefaultTestContainerImage, + }, + Command: []string{"sleep", "60"}, Linux: &runtimeapi.LinuxContainerConfig{ SecurityContext: &runtimeapi.LinuxContainerSecurityContext{ Privileged: privileged,