diff options
| author | Adrian Reber <areber@redhat.com> | 2019-06-25 12:28:18 +0000 |
|---|---|---|
| committer | Adrian Reber <areber@redhat.com> | 2019-06-25 19:42:04 +0200 |
| commit | 95719b6d6b2cf7eae9b60e9a46161a2cbbe588b7 (patch) | |
| tree | c534d72ab5b33956dc226f080204a83dec2f8808 /libpod/container_unsupported.go | |
| parent | 220e169cc1f04a17b25d7af0994715f75be0d249 (diff) | |
| download | podman-95719b6d6b2cf7eae9b60e9a46161a2cbbe588b7.tar.gz podman-95719b6d6b2cf7eae9b60e9a46161a2cbbe588b7.tar.bz2 podman-95719b6d6b2cf7eae9b60e9a46161a2cbbe588b7.zip | |
Add exec after checkpoint/restore test
A container restored from a checkpoint archive used to have the root
file-system mounted with a wrong (new) SELinux label. This made it, for
example, impossible to use 'podman exec' on a restored container.
This test tests exactly this. 'podman exec' after 'podman container restore'.
Unfortunately this test does not fail, even without the patch that fixes
it as the test seems to run in an environment where the SELinux label of
the container root file-system is not relevant. Somehow.
Signed-off-by: Adrian Reber <areber@redhat.com>
Diffstat (limited to 'libpod/container_unsupported.go')
0 files changed, 0 insertions, 0 deletions