containers/buildah
1
0
Fork 0
mirror of https://github.com/containers/buildah.git synced 2026-02-05 09:45:38 +01:00
Code Issues Releases Wiki Activity

Change references to cri-o to point at new repository

Browse Source 
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #993
Approved by: TomSweeneyRedHat
This commit is contained in:
Daniel J Walsh
2018-09-07 09:35:23 -04:00
committed by Atomic Bot
parent 9c8c58c33b
commit 7ea05189e2
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/cni-examples/README.md
View File

@@ -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

2
docs/tutorials/01-intro.md
View File

@@ -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: