vendor: github.com/opencontainers/runc v1.1.6
release notes: https://github.com/opencontainers/runc/releases/tag/v1.1.6 full diff: opencontainers/runc@v1.1.5...v1.1.6 This is the sixth patch release in the 1.1.z series of runc, which fixes a series of cgroup-related issues. Note that this release can no longer be built from sources using Go 1.16. Using a latest maintained Go 1.20.x or Go 1.19.x release is recommended. Go 1.17 can still be used. - systemd cgroup v1 and v2 drivers were deliberately ignoring UnitExist error from systemd while trying to create a systemd unit, which in some scenarios may result in a container not being added to the proper systemd unit and cgroup. - systemd cgroup v2 driver was incorrectly translating cpuset range from spec's resources.cpu.cpus to systemd unit property (AllowedCPUs) in case of more than 8 CPUs, resulting in the wrong AllowedCPUs setting. - systemd cgroup v1 driver was prefixing container's cgroup path with the path of PID 1 cgroup, resulting in inability to place PID 1 in a non-root cgroup. - runc run/start may return "permission denied" error when starting a rootless container when the file to be executed does not have executable bit set for the user, not taking the CAP_DAC_OVERRIDE capability into account. This is a regression in runc 1.1.4, as well as in Go 1.20 and 1.20.1 - cgroup v1 drivers are now aware of misc controller. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
		
							
								
								
									
										14
									
								
								vendor/github.com/opencontainers/runc/libcontainer/user/user.go
									
									
									
										generated
									
									
										vendored
									
									
								
							
							
						
						
									
										14
									
								
								vendor/github.com/opencontainers/runc/libcontainer/user/user.go
									
									
									
										generated
									
									
										vendored
									
									
								
							@@ -280,13 +280,13 @@ func GetExecUserPath(userSpec string, defaults *ExecUser, passwdPath, groupPath
 | 
			
		||||
// found in any entry in passwd and group respectively.
 | 
			
		||||
//
 | 
			
		||||
// Examples of valid user specifications are:
 | 
			
		||||
//     * ""
 | 
			
		||||
//     * "user"
 | 
			
		||||
//     * "uid"
 | 
			
		||||
//     * "user:group"
 | 
			
		||||
//     * "uid:gid
 | 
			
		||||
//     * "user:gid"
 | 
			
		||||
//     * "uid:group"
 | 
			
		||||
//   - ""
 | 
			
		||||
//   - "user"
 | 
			
		||||
//   - "uid"
 | 
			
		||||
//   - "user:group"
 | 
			
		||||
//   - "uid:gid
 | 
			
		||||
//   - "user:gid"
 | 
			
		||||
//   - "uid:group"
 | 
			
		||||
//
 | 
			
		||||
// It should be noted that if you specify a numeric user or group id, they will
 | 
			
		||||
// not be evaluated as usernames (only the metadata will be filled). So attempting
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user