Blame README.md

595bef4
# cri-o
595bef4
d75d3d7
This is the cri-o daemon as a system container.
d75d3d7
d75d3d7
## Building the image from source:
d75d3d7
d75d3d7
```
d75d3d7
# git clone https://github.com/projectatomic/atomic-system-containers
d75d3d7
# cd atomic-system-containers/cri-o
d75d3d7
# docker build -t crio .
d75d3d7
```
d75d3d7
d75d3d7
## Running the system container, with the atomic CLI:
d75d3d7
d75d3d7
Pull from registry into ostree:
d75d3d7
d75d3d7
```
d75d3d7
# atomic pull --storage ostree $REGISTRY/crio
d75d3d7
```
d75d3d7
d75d3d7
Or alternatively, pull from local docker:
d75d3d7
d75d3d7
```
d75d3d7
# atomic pull --storage ostree docker:crio:latest
d75d3d7
```
d75d3d7
d75d3d7
Install the container:
d75d3d7
d75d3d7
Currently we recommend using --system-package=no to avoid having rpmbuild create an rpm file
d75d3d7
during installation. This flag will tell the atomic CLI to fall back to copying files to the
d75d3d7
host instead.
d75d3d7
d75d3d7
```
d75d3d7
# atomic install --system --system-package=no --name=crio ($REGISTRY)/crio
d75d3d7
```
d75d3d7
d75d3d7
Start as a systemd service:
d75d3d7
d75d3d7
```
d75d3d7
# systemctl start crio
d75d3d7
```
d75d3d7
d75d3d7
Stopping the service
d75d3d7
d75d3d7
```
d75d3d7
# systemctl stop crio
d75d3d7
```
d75d3d7
d75d3d7
Removing the container
d75d3d7
d75d3d7
```
d75d3d7
# atomic uninstall crio
d75d3d7
```
d75d3d7