cri-o/oci
Antonio Murdaca c316e5d8cf
oci: respect process spec on exec
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>
2017-10-24 22:39:17 +02:00
..
container.go oci: respect process spec on exec 2017-10-24 22:39:17 +02:00
finished.go oci: fix build condition 2017-08-03 20:20:38 +02:00
finished_32.go oci: fix type mismatch on some platform/arch 2017-07-17 15:31:19 +02:00
history.go use an in memory store for containers 2016-09-19 13:11:36 +02:00
memory_store.go oci: more grep'able interface name 2017-04-19 16:12:59 -04:00
oci.go oci: respect process spec on exec 2017-10-24 22:39:17 +02:00
store.go oci: more grep'able interface name 2017-04-19 16:12:59 -04:00