This repository has been archived by the owner on May 12, 2021. It is now read-only.
exec: A process can be run on a created container #120
Assignees
Comments
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Mar 27, 2018
If a container is not running, but created/ready instead, this means a container process exists and that we can actually exec another process inside this container. The container does not have to be in running state. Fixes kata-containers#120 Signed-off-by: Sebastien Boeuf <[email protected]>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Mar 29, 2018
If a container is not running, but created/ready instead, this means a container process exists and that we can actually exec another process inside this container. The container does not have to be in running state. Fixes kata-containers#120 Signed-off-by: Sebastien Boeuf <[email protected]>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Mar 29, 2018
If a container is not running, but created/ready instead, this means a container process exists and that we can actually exec another process inside this container. The container does not have to be in running state. Fixes kata-containers#120 Signed-off-by: Sebastien Boeuf <[email protected]>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Mar 29, 2018
If a container is not running, but created/ready instead, this means a container process exists and that we can actually exec another process inside this container. The container does not have to be in running state. Fixes kata-containers#120 Signed-off-by: Sebastien Boeuf <[email protected]>
zklei
pushed a commit
to zklei/runtime
that referenced
this issue
Jun 13, 2019
add a CONTRIBUTING.md for this repo Fixes: kata-containers#120 Signed-off-by: Ruidong Cao <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If a container is not
running, butcreated/readyinstead, this means a container process exists and that we can actuallyexecanother process inside this container. The container does not have to be inrunningstate.The text was updated successfully, but these errors were encountered: