ATIX AG
  • Services
    • Consulting
      • Linux Platform Operations​
      • Infrastructure Automation
      • Container Platforms and Cloud
      • DevOps Processes, Tooling and Culture
      • Cloud Native Software Development
    • Products
      • orcharhino
        • About orcharhino
        • Support
        • orcharhino operation
      • Hangar
        • About Hangar
        • Start now for free with Hangar
        • Hangar Documentation
        • Hangar Roadmap
        • Hangar Changelog
        • Hangar Community
    • Technologies
      • Ansible
      • AWX and Ansible Automation Platform
      • Docker
      • Foreman
      • GitLab
      • Istio
      • Kubernetes
      • Linux Distributions
      • OpenShift
      • Puppet
      • OpenVox
      • Rancher
      • Rundeck
      • SaltStack
      • SUSE Manager
      • Terraform
  • Trainings
    • Ansible Training
    • AWX Training
    • Docker & Container Training
    • Git Training
    • Go Training (Golang)
    • Istio Training
    • Kubernetes Training
    • OpenShift Training
    • orcharhino Training
    • Puppet Trainings
    • Terraform Training
  • Events
    • Webinars
  • Blog
  • Company
    • About Us
    • References
    • Corporate values
    • Social engagement
    • Newsroom
    • Newsletter
    • Contact us
  • Career
  • German
  • Click to open the search input field Click to open the search input field Search
  • Menu Menu
Docker zu CRIO-O

Switching from Docker to CRI-O

In this blog post, we’d like to answer some FAQs regarding the change from Docker to CRI-O. Here we go!

First and foremost: how do I switch from Docker to CRI-O?

The answer is not quite straightforward, unfortunately. It depends on several factors.

A Kubernetes cluster can use CRI-O as a container runtime (OpenShift 4.x does so, for example).

Addressing image builders: CRI-O does not offer the toolset for building images. CRI-O is a daemon, only accessible through the Container Runtime Interface (CRI).

CRI-O = CRI + OCI
This means that it creates containers from images compliant to the standards defined by the open container initiative (OCI).

Is Podman a CLI to CRI-O?

No. crictl queries the CRI on the terminal. The backends are different, there is a large overlap between contributors and the design is similar (pods in mind).

How can I try it?

alias docker=podman

Do I have to learn new commands?

It’s not necessary, but if you really want to:

podman manages containers

buildah creates container images

skopeo manages images in registries

What do I lose?

For a long time, there was no replacement for docker-compose. Now, there is a community project podman-compose. We are still evaluating to what extent it can serve as a substitute.

Conclusion

k8s cluster → CRI → docker (containerd) / CRI-O
CLI → docker / podman, buildah, skopeo / rkt

You might also like
container building with kaniko Container building with Kaniko
The future of software architecture: focus on event-driven architecture Docker: Storing apps in containers
Was ist WASI WebAssembly on the Server Side: What is WASI?
Workshops in the Cloud – What Ansible, Docker and the GitLab CI/CD offer for this
The future of software architecture: focus on event-driven architecture Creation of Foreman RPM packages with Docker containers
The future of software architecture: focus on event-driven architecture The future of software architecture: focus on event-driven architecture

Jan Bundesmann
+ postsBio
  • Jan Bundesmann
    https://atix.de/en/blog/author/janb/
    ATIX at ConfigMgmtCamp 2024
  • Jan Bundesmann
    https://atix.de/en/blog/author/janb/
    Registers and Macros in Vim
  • Jan Bundesmann
    https://atix.de/en/blog/author/janb/
    Installing OpenShift through Foreman
  • Jan Bundesmann
    https://atix.de/en/blog/author/janb/
    Mouse-free

On this page

ISO 27001 Certified Download ISO 27001 Certificate
ISO 9001 Certified Download ISO 9001 Certificate
Newsletter
Never miss anything again. Sign up for the ATIX newsletter!
Sign up now
Blog
  • Blog Start Page
  • ATIX Insights
  • Cloud Native
  • Container Plattformen und Cloud
  • DevOps
  • Hangar
  • Infrastructure Automation
  • Linux Platform Operations
  • orcharhino
Privacy & Legal

Privacy Policy

Imprint

Terms and Conditions

B2B

Twitter     Facebook    LinkedIn    Youtube     mastodon=

© Copyright – ATIX AG

Scroll to top Scroll to top Scroll to top