a32c3d4b9a
This patch fixes exec to use the original (start-time) process exec configuration. Otherwise, we were creating a brand new spec process w/o additional groups for instance. Spotted while integrating CRI-O with cri-test...The test was failing with: ``` • Failure [10.640 seconds] [k8s.io] Security Context /home/amurdaca/go/src/github.com/kubernetes-incubator/cri-tools/pkg/framework/framework.go:72 bucket /home/amurdaca/go/src/github.com/kubernetes-incubator/cri-tools/pkg/validate/security_context.go:407 runtime should support SupplementalGroups [It] /home/amurdaca/go/src/github.com/kubernetes-incubator/cri-tools/pkg/validate/security_context.go:272 Expected <[]string | len:1, cap:1>: ["0"] to contain element matching <string>: 1234 ``` Signed-off-by: Antonio Murdaca <runcom@redhat.com> |
||
---|---|---|
.. | ||
apparmor | ||
seccomp | ||
config.go | ||
container_attach.go | ||
container_create.go | ||
container_exec.go | ||
container_execsync.go | ||
container_list.go | ||
container_portforward.go | ||
container_remove.go | ||
container_start.go | ||
container_stats.go | ||
container_stats_list.go | ||
container_status.go | ||
container_stop.go | ||
container_updateruntimeconfig.go | ||
image_fs_info.go | ||
image_list.go | ||
image_pull.go | ||
image_remove.go | ||
image_status.go | ||
inspect.go | ||
inspect_test.go | ||
naming.go | ||
runtime_status.go | ||
sandbox_list.go | ||
sandbox_network.go | ||
sandbox_remove.go | ||
sandbox_run.go | ||
sandbox_status.go | ||
sandbox_stop.go | ||
secrets.go | ||
server.go | ||
utils.go | ||
version.go |