@@ -1228,7 +1228,7 @@ metadata:
12281228  name : profile1 
12291229spec :
12301230  defaultAction : SCMP_ACT_ERRNO 
1231-   baseProfileName : runc-v1.2.5  
1231+   baseProfileName : runc-v1.2.6  
12321232  syscalls :
12331233    - action : SCMP_ACT_ALLOW 
12341234      names :
@@ -1294,7 +1294,7 @@ metadata:
12941294  name: profile1 
12951295spec: 
12961296  defaultAction: SCMP_ACT_ERRNO 
1297-   baseProfileName: oci://ghcr.io/security-profiles/runc:v1.2.5  
1297+   baseProfileName: oci://ghcr.io/security-profiles/runc:v1.2.6  
12981298` ` ` 
12991299
13001300The resulting profile `profile1` will then contain all base syscalls from the 
@@ -1656,24 +1656,24 @@ The `spoc` client is able to pull security profiles from OCI artifact compatible
16561656registries. To do that, just run `spoc pull` :
16571657
16581658` ` ` console
1659- > spoc pull ghcr.io/security-profiles/runc:v1.2.5  
1660- 16:32:29.795597 Pulling profile from: ghcr.io/security-profiles/runc:v1.2.5  
1659+ > spoc pull ghcr.io/security-profiles/runc:v1.2.6  
1660+ 16:32:29.795597 Pulling profile from: ghcr.io/security-profiles/runc:v1.2.6  
1661166116:32:29.795610 Verifying signature 
16621662
1663- Verification for ghcr.io/security-profiles/runc:v1.2.5  -- 
1663+ Verification for ghcr.io/security-profiles/runc:v1.2.6  -- 
16641664The following checks were performed on each of these signatures: 
16651665  - Existence of the claims in the transparency log was verified offline 
16661666  - The code-signing certificate was verified using trusted certificate authority certificates 
16671667
16681668[{"critical":{"identity":{"docker-reference":"ghcr.io/security-profiles/runc"},…}}] 
1669166916:32:33.208695 Creating file store in: /tmp/pull-3199397214 
1670- 16:32:33.208713 Verifying reference: ghcr.io/security-profiles/runc:v1.2.5  
1670+ 16:32:33.208713 Verifying reference: ghcr.io/security-profiles/runc:v1.2.6  
1671167116:32:33.208718 Creating repository for ghcr.io/security-profiles/runc 
1672- 16:32:33.208742 Using tag: v1.2.5  
1672+ 16:32:33.208742 Using tag: v1.2.6  
1673167316:32:33.208743 Copying profile from repository 
1674167416:32:34.119652 Reading profile 
1675167516:32:34.119677 Trying to unmarshal seccomp profile 
1676- 16:32:34.120114 Got SeccompProfile: runc-v1.2.5  
1676+ 16:32:34.120114 Got SeccompProfile: runc-v1.2.6  
1677167716:32:34.120119 Saving profile in: /tmp/profile.yaml 
16781678` ` ` 
16791679
@@ -1801,15 +1801,15 @@ The Security Profiles Operator will try to pull the correct profile by using
18011801way, for example if a profile does not support any platform :
18021802
18031803` ` ` 
1804- > spoc pull ghcr.io/security-profiles/runc:v1.2.5  
1805- 11:07:14.788840 Pulling profile from: ghcr.io/security-profiles/runc:v1.2.5  
1804+ > spoc pull ghcr.io/security-profiles/runc:v1.2.6  
1805+ 11:07:14.788840 Pulling profile from: ghcr.io/security-profiles/runc:v1.2.6  
1806180611:07:14.788852 Verifying signature 
18071807… 
1808180811:07:17.559037 Copying profile from repository 
1809180911:07:18.359152 Trying to read profile: profile-linux-amd64.yaml 
1810181011:07:18.359209 Trying to read profile: profile.yaml 
1811181111:07:18.359224 Trying to unmarshal seccomp profile 
1812- 11:07:18.359728 Got SeccompProfile: runc-v1.2.5  
1812+ 11:07:18.359728 Got SeccompProfile: runc-v1.2.6  
1813181311:07:18.359732 Saving profile in: /tmp/profile.yaml 
18141814` ` ` 
18151815
0 commit comments