From 95cb7a11f124b5d095e95a8928d752f38d6b375d Mon Sep 17 00:00:00 2001
From: Daniel J Walsh <dwalsh@redhat.com>
Date: Sat, 2 Dec 2017 06:00:53 -0500
Subject: 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
---
 test/kpod_pause.bats | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'test')

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 ]
 }
-- 
cgit v1.2.3-54-g00ecf