Introduction

corail is a small, daemonless container engine for Linux and macOS (Intel and Silicon).

What is corail?

corail runs containers from OCI images. It pulls from any registry, unpacks the layers, and starts your process. Each corail command does its work and exits.

On Linux it is one static binary. Containers run rootless by default, in their own namespaces and cgroups, so you do not need sudo to try it.

On macOS (Intel and Silicon) the same commands run Linux images in a microVM. One VM stays up per store, so a later corail ps sees the containers a previous corail run started.

OCI registry

any registry, image layers

corail

one static binary. Pulls, unpacks, starts, then exits.

Linux

namespaces and cgroups, rootless

macOS

one microVM per store. The same binary runs inside it.

capsule

your process, one running container

On Linux, corail starts the capsule on the host. On macOS, it starts the capsule inside a Linux microVM that stays up for that store.

The tools

  • corail: the engine. Pull images, run, stop and inspect containers (called capsules).
  • coraild: the control plane. It keeps groups of capsules, called atolls, running as described in a reef.json.
  • recify: the command-line client for coraild, in the spirit of kubectl.
  • sonar: a terminal view of a running atoll.

Vocabulary

  • capsule: one running container.
  • atoll: a group of capsules that share a network namespace and are scheduled together.
  • reef.json: the file that describes an atoll.

The commands and flags follow Docker's, so corail run, ps, logs, exec, stop and rm behave the way you expect.

Platforms

  • Linux (x86_64, aarch64): runs containers natively.
  • macOS (Intel and Silicon): runs Linux images in a microVM.
  • Windows: not planned.

Where to go next

  • Commands: every corail subcommand and flag.
  • Reference: the reef.json format, and coraild and recify.