summaryrefslogtreecommitdiff
path: root/test/kpod_pause.bats
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2017-12-02 06:00:53 -0500
committerAtomic Bot <atomic-devel@projectatomic.io>2017-12-04 17:35:14 +0000
commit95cb7a11f124b5d095e95a8928d752f38d6b375d (patch)
tree58effbc3756def52bdc1d1dd5fdeb78c29f9a43c /test/kpod_pause.bats
parent55c8b69d8f80b31c5748c1bd50c812aaa0e6c1c7 (diff)
downloadpodman-95cb7a11f124b5d095e95a8928d752f38d6b375d.tar.gz
podman-95cb7a11f124b5d095e95a8928d752f38d6b375d.tar.bz2
podman-95cb7a11f124b5d095e95a8928d752f38d6b375d.zip
kpod create should not do an OCI Init
We need to differentiate between a kpod create and a kpod start kpod create should create all of the data for libpod, but kpod start should generate content for OCI Runtime (runc) in order to run. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> Closes: #96 Approved by: mheon
Diffstat (limited to 'test/kpod_pause.bats')
-rw-r--r--test/kpod_pause.bats4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/kpod_pause.bats b/test/kpod_pause.bats
index 3d6ab7b91..d26f0e4e1 100644
--- a/test/kpod_pause.bats
+++ b/test/kpod_pause.bats
@@ -23,7 +23,7 @@ function teardown() {
}
@test "pause a created container by id" {
- run bash -c "${KPOD_BINARY} ${KPOD_OPTIONS} create $BB ls"
+ run bash -c "${KPOD_BINARY} ${KPOD_OPTIONS} run -d $BB sleep 60"
echo "$output"
[ "$status" -eq 0 ]
ctr_id="$output"
@@ -33,7 +33,7 @@ function teardown() {
run bash -c "${KPOD_BINARY} ${KPOD_OPTIONS} unpause $ctr_id"
echo "$output"
[ "$status" -eq 0 ]
- run bash -c "${KPOD_BINARY} ${KPOD_OPTIONS} rm $ctr_id"
+ run bash -c "${KPOD_BINARY} ${KPOD_OPTIONS} rm -f $ctr_id"
echo "$output"
[ "$status" -eq 0 ]
}