Removes instances of s/cc-runtime for kata per @devimc

Signed-off-by: Michael Vincerra <michael.vincerra@intel.com>
This commit is contained in:
Michael Vincerra
2018-07-12 10:06:35 -07:00
parent dada6c0a4f
commit e23dcbbe9c
+2 -2
View File
@@ -87,11 +87,11 @@ More information about Docker in |CLOSIA|.
############################################# #############################################
Docker on |CLOSIA| provides a docker.service service file to start the Docker Docker on |CLOSIA| provides a docker.service service file to start the Docker
daemon. The daemon will use runc or s/cc-runtime/kata-runtime depending on daemon. The daemon will use runc or kata-runtime depending on
the environment: the environment:
If you are running |CL| on bare metal or on a VM with Nested If you are running |CL| on bare metal or on a VM with Nested
Virtualization activated, Docker will use s/cc-runtime/kata-runtime as the Virtualization activated, Docker will use kata-runtime as the
default runtime. If you are running |CL| on a VM without Nested default runtime. If you are running |CL| on a VM without Nested
Virtualization, Docker will use runc as the default runtime. It is not Virtualization, Docker will use runc as the default runtime. It is not
necessary to manually configure the runtime for Docker, since Docker itself necessary to manually configure the runtime for Docker, since Docker itself