container/cri-o
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The cri-o package
22 commits 6 branches 0 tags 65 KiB
  • Dockerfile 59%
  • Shell 41%
Find a file
Exact
Mohan Boddu 4c9767edae "Bump RELEASE for automatic rebuild"
2018-09-21 15:58:43 +00:00
config.json.template cri-o: sync from upstream 2018-05-16 15:48:33 +02:00
config.json.template.orig Initial import (rhbz#1511605) 2017-11-11 10:50:32 +01:00
Dockerfile "Bump RELEASE for automatic rebuild" 2018-09-21 15:58:43 +00:00
manifest.json cri-o: sync from upstream 2018-05-16 15:48:33 +02:00
README.md Initial import (rhbz#1511605) 2017-11-11 10:50:32 +01:00
run.sh cri-o: sync from upstream 2018-05-16 15:48:33 +02:00
service.template sync with upstream 2018-01-10 09:53:53 +01:00
set_mounts.sh Initial import (rhbz#1511605) 2017-11-11 10:50:32 +01:00
tmpfiles.template sync with upstream 2018-01-10 09:53:53 +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