From 7ea05189e249f3595d53b9ab75d12790994405f3 Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Fri, 7 Sep 2018 09:35:23 -0400 Subject: [PATCH] Change references to cri-o to point at new repository Signed-off-by: Daniel J Walsh Closes: #993 Approved by: TomSweeneyRedHat --- docs/cni-examples/README.md | 2 +- docs/tutorials/01-intro.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/cni-examples/README.md b/docs/cni-examples/README.md index 4e6b87307..f97adc62f 100644 --- a/docs/cni-examples/README.md +++ b/docs/cni-examples/README.md @@ -29,7 +29,7 @@ install those plugins, try running: ``` If you've already installed a CNI configuration (for example, for -[CRI-O](https://github.com/kubernetes-incubator/cri-o)), it'll probably just +[CRI-O](https://github.com/kubernetes-sigs/cri-o)), it'll probably just work, but to install these sample configuration files: ``` mkdir -p /etc/cni/net.d diff --git a/docs/tutorials/01-intro.md b/docs/tutorials/01-intro.md index 24541bfa8..c4fcb50a0 100644 --- a/docs/tutorials/01-intro.md +++ b/docs/tutorials/01-intro.md @@ -35,7 +35,7 @@ What can we do with this new container? Let's try running bash: # buildah run $container bash -Notice we get a new shell prompt because we are running a bash shell inside of the container. It should be noted that `buildah run` is primarily intended for helping debug during the build process. A runtime like runc or a container interface like [CRI-O](https://github.com/kubernetes-incubator/cri-o) is more suited for starting containers in production. +Notice we get a new shell prompt because we are running a bash shell inside of the container. It should be noted that `buildah run` is primarily intended for helping debug during the build process. A runtime like runc or a container interface like [CRI-O](https://github.com/kubernetes-sigs/cri-o) is more suited for starting containers in production. Be sure to `exit` out of the container and let's try running something else: