aljaz/kata-containers
1
0
Fork 0
mirror of https://github.com/aljazceru/kata-containers.git synced 2026-01-16 21:04:25 +01:00
Code Issues Packages Projects Releases Wiki Activity
303 Commits 30 Branches 115 Tags
7465fde3086ed10a7d00fbb02c16fc1047743588
Go to file
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Download ZIP Download TAR.GZ Download BUNDLE
katacontainers bot 7465fde308 release: Kata Containers 1.7.0-alpha1 
- image-builder: share the mkfs configuration file
- rootfs-builder: add rootfs.sh DOCKER_RUNTIME env var
- rootfs-builder: SELinux relabel container volumes
- image-builder: add fs type
- image-builder: re-implement image builder script
- builder: Pass the DEBUG flag when using docker
- Add chrony to image
- Print attempt number after max check

88b8523 image-builder: share the mkfs configuration file
77fb808 image-builder: check format_loop return code
8debe95 image-builder: add fs type
c72c954 rootfs-builder: add rootfs.sh DOCKER_RUNTIME env var
c1d9510 rootfs-builder: SELinux relabel container volumes
d8cdd88 image-builder: re-implement image builder script
f32ae14 tests: remove DAX env variable
f355c02 tests: enable DEBUG
6c7f307 image-builder: add xfsprogs to Dockerfile
ad6e1a9 scripts: implement error function
0d2ba47 builder: Pass the DEBUG flag when using docker
e16ff37 chrony: Comment out any NTP sources for chrony
3df19ff chrony: Add virtual PTP as source for chrony
ad5d879 rootfs: Print attempt number after max check
8fe6405 rootfs: Include chrony in the Dockerfile images
0b33519 rootfs: add PACKAGE var to debian config
510ddd2 rootfs: Add chrony service to rootfs

Signed-off-by: katacontainers bot <katacontainersbot@katacontainers.io>
2019-04-17 17:38:46 +00:00
.ci
setup: Add make and gcc as dependencies
2018-12-14 08:09:52 -06:00
image-builder
image-builder: share the mkfs configuration file
2019-04-01 09:18:28 -06:00
initrd-builder
initrd-builder: make initrd_builder.sh idempotent
2018-06-29 15:08:56 +01:00
rootfs-builder
Merge pull request #269 from stefanha/rootfs-DOCKER_RUNTIME-env-var
2019-04-01 10:38:50 -06:00
scripts
scripts: implement error function
2019-03-25 08:19:13 -06:00
tests
tests: remove DAX env variable
2019-03-26 09:02:45 -06:00
.gitignore
image-builder: fill out device namespace information into kata image
2019-03-13 13:05:06 -06:00
.travis.yml
travis: remove AGENT_INIT env combinations
2018-10-02 12:59:18 +02:00
CODE_OF_CONDUCT.md
CoC: Add Code of Conduct
2017-12-04 23:35:38 +01:00
CONTRIBUTING.md
Docs : Add minimal contribution guidelines
2018-01-30 22:01:48 +05:30
LICENSE
Initial commit
2017-11-13 12:24:56 +01:00
Makefile
mage-builder: remove -s option and IMG_SIZE envar
2019-03-13 13:05:06 -06:00
README.md
docs: add s390 to the compatibility matrix
2018-12-17 10:39:09 +01:00
VERSION
release: Kata Containers 1.7.0-alpha1
2019-04-17 17:38:46 +00:00

README.md

Build Status

osbuilder

Introduction

The Kata Containers runtime creates a virtual machine (VM) to isolate a set of container workloads. The VM requires a guest kernel and a guest operating system ("guest OS") to boot and create containers inside the guest environment.

This repository contains tools to create a guest OS disk image.

Terms

This section describes the terms used for all documentation in this repository.

  • rootfs

    The root filesystem or "rootfs" is a slight misnomer as it is not a true filesystem. It is a tree of files contained in a particular directory, which represents the root disk layout. A rootfs can be turned into either an image or an initrd.

    See the rootfs creation section.

  • "Guest OS" (or "Guest Image")

    A "virtual disk" or "disk image" built from a rootfs. It contains a filesystem that is used by the VM, in conjunction with a guest kernel, to create an environment to host the container. Neither the guest OS nor the guest kernel need to be the same as the host operating system.

    See the image creation section.

  • initrd (or "initramfs")

    A compressed cpio(1) archive, created from a rootfs which is loaded into memory and used as part of the Linux startup process. During startup, the kernel unpacks it into a special instance of a tmpfs that becomes the initial root filesystem.

    See the initrd creation section.

  • "Base OS"

    A particular version of a Linux distribution used to create a rootfs from.

Usage

The top-level Makefile contains an example of how to use the available components.

By default, components will run on the host system. However, some components offer the ability to run from within Docker (for ease of setup) by setting the USE_DOCKER=true variable.

For more detailed information, consult the documentation for a particular component.

Rootfs creation

This section shows how to build a basic rootfs using the default distribution. For further details, see the rootfs builder documentation.

Rootfs with systemd as init

$ sudo -E PATH=$PATH make USE_DOCKER=true rootfs

Rootfs with the agent as init

$ sudo -E PATH=$PATH make USE_DOCKER=true AGENT_INIT=yes rootfs

Image creation

This section shows how to create an image from the already-created rootfs. For further details, see the image builder documentation.

Image with systemd as init

$ sudo -E PATH=$PATH make USE_DOCKER=true image

Image with the agent as init

$ sudo -E PATH=$PATH make USE_DOCKER=true AGENT_INIT=yes image

Initrd creation

To create an initrd from the already-created rootfs with the agent acting as the init daemon:

$ sudo -E PATH=$PATH make AGENT_INIT=yes initrd

For further details, see the initrd builder documentation.

Tests

$ make test

For further details, see the tests documentation.

Platform-Distro Compatibility Matrix

Alpine CentOS ClearLinux Debian/Ubuntu EulerOS Fedora openSUSE
ARM64 ✔️ ✔️ ✔️ ✔️ ✔️
PPC64le ✔️ ✔️ ✔️ ✔️ ✔️ ✔️
s390x ✔️ ✔️ ✔️
x86_64 ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️
Description
No description provided
Readme Apache-2.0 71 MiB
Languages
Rust 57%
Go 27%
Shell 8%
RPC 5.9%
Makefile 1%
Other 1.1%