@@ -1595,7 +1595,7 @@ metadata:
15951595 name: profile1
15961596spec:
15971597 defaultAction: SCMP_ACT_ERRNO
1598- baseProfileName: runc-v1.3.2
1598+ baseProfileName: runc-v1.3.3
15991599 syscalls:
16001600 - action: SCMP_ACT_ALLOW
16011601 names:
@@ -1661,7 +1661,7 @@ metadata:
16611661 name : profile1
16621662spec :
16631663 defaultAction : SCMP_ACT_ERRNO
1664- baseProfileName : oci://ghcr.io/security-profiles/runc:v1.3.2
1664+ baseProfileName : oci://ghcr.io/security-profiles/runc:v1.3.3
16651665` ` `
16661666
16671667The resulting profile ` profile1` will then contain all base syscalls from the
@@ -2023,24 +2023,24 @@ The `spoc` client is able to pull security profiles from OCI artifact compatible
20232023registries. To do that, just run `spoc pull` :
20242024
20252025` ` ` console
2026- > spoc pull ghcr.io/security-profiles/runc:v1.3.2
2027- 16:32:29.795597 Pulling profile from: ghcr.io/security-profiles/runc:v1.3.2
2026+ > spoc pull ghcr.io/security-profiles/runc:v1.3.3
2027+ 16:32:29.795597 Pulling profile from: ghcr.io/security-profiles/runc:v1.3.3
2028202816:32:29.795610 Verifying signature
20292029
2030- Verification for ghcr.io/security-profiles/runc:v1.3.2 --
2030+ Verification for ghcr.io/security-profiles/runc:v1.3.3 --
20312031The following checks were performed on each of these signatures:
20322032 - Existence of the claims in the transparency log was verified offline
20332033 - The code-signing certificate was verified using trusted certificate authority certificates
20342034
20352035[{"critical":{"identity":{"docker-reference":"ghcr.io/security-profiles/runc"},…}}]
2036203616:32:33.208695 Creating file store in: /tmp/pull-3199397214
2037- 16:32:33.208713 Verifying reference: ghcr.io/security-profiles/runc:v1.3.2
2037+ 16:32:33.208713 Verifying reference: ghcr.io/security-profiles/runc:v1.3.3
2038203816:32:33.208718 Creating repository for ghcr.io/security-profiles/runc
2039- 16:32:33.208742 Using tag: v1.3.2
2039+ 16:32:33.208742 Using tag: v1.3.3
2040204016:32:33.208743 Copying profile from repository
2041204116:32:34.119652 Reading profile
2042204216:32:34.119677 Trying to unmarshal seccomp profile
2043- 16:32:34.120114 Got SeccompProfile: runc-v1.3.2
2043+ 16:32:34.120114 Got SeccompProfile: runc-v1.3.3
2044204416:32:34.120119 Saving profile in: /tmp/profile.yaml
20452045` ` `
20462046
@@ -2168,15 +2168,15 @@ The Security Profiles Operator will try to pull the correct profile by using
21682168way, for example if a profile does not support any platform :
21692169
21702170` ` `
2171- > spoc pull ghcr.io/security-profiles/runc:v1.3.2
2172- 11:07:14.788840 Pulling profile from: ghcr.io/security-profiles/runc:v1.3.2
2171+ > spoc pull ghcr.io/security-profiles/runc:v1.3.3
2172+ 11:07:14.788840 Pulling profile from: ghcr.io/security-profiles/runc:v1.3.3
2173217311:07:14.788852 Verifying signature
21742174…
2175217511:07:17.559037 Copying profile from repository
2176217611:07:18.359152 Trying to read profile: profile-linux-amd64.yaml
2177217711:07:18.359209 Trying to read profile: profile.yaml
2178217811:07:18.359224 Trying to unmarshal seccomp profile
2179- 11:07:18.359728 Got SeccompProfile: runc-v1.3.2
2179+ 11:07:18.359728 Got SeccompProfile: runc-v1.3.3
2180218011:07:18.359732 Saving profile in: /tmp/profile.yaml
21812181` ` `
21822182
0 commit comments