run-prepared: restarting exited pods

[Shashwatsh]

Environment
Linux ubuntu-1gb-blr1-01 4.4.0-83-generic # 106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.4.0-83-generic x86_64
--
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
--
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

What did you do?

root@ubuntu-1gb-blr1-01:/# rkt run quay.io/coreos/alpine-sh --interactive
/ # ls
bin      dev      etc      home     lib      linuxrc  media    mnt      proc     root     run      sbin     sys      tmp      usr      var
/ # }}}Container rkt-0ea19d08-0cc8-4e90-8997-051764083fc0 terminated by signal KILL.
root@ubuntu-1gb-blr1-01:/#
root@ubuntu-1gb-blr1-01:/# rkt list
UUID		APP		IMAGE NAME			STATE	CREATED		STARTED		NETWORKS
0ea19d08	alpine-sh	quay.io/coreos/alpine-sh:latest	exited	34 seconds ago	34 seconds ago

root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared

What did you expect to see?
well, a restarted pod
i want to re-run an exit'd pod
What did you see instead?

root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared

[lucab]

As the documentation says, run-prepared is meant to be used with prepare instead of run. You cannot "restart a pod" as it will mess with previous logs, mounts and volumes. You can however re-run it from scratch by reusing the same pod manifest.

[Shashwatsh]

restarting pods; is this feature ever gonna be in rkt?

[lucab]

I think it clashes quite a bit with design assumptions about pod lifecycle and identity, but if you concrete ideas/proposals on how to address those behavioral details we'll be happy to discuss.

[Shashwatsh]

I'm closing this issue. i have no idea why i created this issue in the first place, perhaps maybe i had a better proposal/idea back then but it's gone now.