From 0acf99a85779443ac27964e8773882cdffc6303b Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Tue, 26 Nov 2024 03:53:38 +0100 Subject: [PATCH] Fix CRI-O name (#16) Signed-off-by: Sascha Grunert --- docs/spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spec.md b/docs/spec.md index 68e5dab..52f2bcc 100644 --- a/docs/spec.md +++ b/docs/spec.md @@ -35,7 +35,7 @@ Next push the artifact to the OCI registry(Harbor, Docker Hub, etc.), and use th ### PULL & SERVE -The container runtime(containerd, cri-o, etc) pulls the model artifact from the OCI registry, and mounts the model artifact as a read-only volume. Therefore, distributed model can use the P2P technology(Dragonfly, Kraken, etc) to reduce the pressure on the registry and preheat the model artifact into each node. If the model artifact is already present on the node, the container runtime can reuse the model artifact to mount different containers in the same node. +The container runtime(containerd, CRI-O, etc) pulls the model artifact from the OCI registry, and mounts the model artifact as a read-only volume. Therefore, distributed model can use the P2P technology(Dragonfly, Kraken, etc) to reduce the pressure on the registry and preheat the model artifact into each node. If the model artifact is already present on the node, the container runtime can reuse the model artifact to mount different containers in the same node. ![pull-serve](./img/pull-and-serve.png)