History

Giuseppe Scrivano b1b380d67b syscontainer, centos: create /var/run/crio Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>		2018-01-09 18:00:43 +01:00
..
Dockerfile	contrib: import system containers	2017-12-02 12:24:40 +01:00
README.md	contrib: import system containers	2017-12-02 12:24:40 +01:00
cccp.yml	contrib: import system containers	2017-12-02 12:24:40 +01:00
config.json.template	contrib: import system containers	2017-12-02 12:24:40 +01:00
manifest.json	contrib: import system containers	2017-12-02 12:24:40 +01:00
run.sh	syscontainer, centos: read env variables from files	2018-01-04 20:14:52 +01:00
service.template	contrib: import system containers	2017-12-02 12:24:40 +01:00
set_mounts.sh	contrib: import system containers	2017-12-02 12:24:40 +01:00
tmpfiles.template	syscontainer, centos: create /var/run/crio	2018-01-09 18:00:43 +01:00

README.md

cri-o

This is the cri-o daemon as a system container.

Building the image from source:

# git clone https://github.com/projectatomic/atomic-system-containers
# cd atomic-system-containers/cri-o
# docker build -t crio .

Running the system container, with the atomic CLI:

Pull from registry into ostree:

# atomic pull --storage ostree $REGISTRY/crio

Or alternatively, pull from local docker:

# atomic pull --storage ostree docker:crio:latest

Install the container:

Currently we recommend using --system-package=no to avoid having rpmbuild create an rpm file during installation. This flag will tell the atomic CLI to fall back to copying files to the host instead.

# atomic install --system --system-package=no --name=crio ($REGISTRY)/crio

Start as a systemd service:

# systemctl start crio

Stopping the service

# systemctl stop crio

Removing the container

# atomic uninstall crio

Binary version

You can find the image automatically built as: registry.centos.org/projectatomic/cri-o:latest