nix2aci

KO | EN

gitlite — search

#javascript #hacktoberfest #react #ai #golang #machine-learning #docker #macos #windows #cli #kubernetes #pytorch #ios #openai

(★ 25)

Machinery for creating and running ACIs on Linux systems where Nix(OS) and rkt are available

nix2aci 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# nix2aci

[![Build Status](https://travis-ci.org/steveeJ/nix2aci.svg?branch=master)](https://travis-ci.org/steveeJ/nix2aci)

Let's use Nix' super powers to build [App Container Images](http://github.com/appc/spec)!

This project should be understood as a proof of concept until stated otherwise.
You can expect this README to be minimal but it should always contain working examples.

## ACI Build Requirements
* local copy of this repository
* [nix](http://www.nixos.org/nix) plus the skills to query package names
* python

## ACI Runtime Requirements
* [coreos/rkt](https://github.com/coreos/rkt/)

## Signing Requirements
~~Including the signing process into the nix workflow seems quite tedious and is not fully satisfactory at this point. I chose to setup a key for the nix build environment. The downside is that every build can read and use the key which is bad if the build system is compromised in any way.~~

~~Please take a look at [the included script](scripts/setup-gpg.sh), which can be used to do the preparation.~~
In order to sign your build you need to have a working setup of gpg with `gpg2` being in your path. After the build, you can run the script(s) located in at `result*/postprocess.sh` and the signatures will be created along with symlinks to the ACI.

# Building ACIs
There's more than one way to build and use ACIs with Nix, because the filesystem structure allows for side-by-side installations of almost any package. Every package (version) is stored at $NIX\_STORE identified by hash, and can be pulled into different profiles independently. These profiles could be copied, but it should also be possible to bind-mount the host versions into the containers.

## Thin ACIs
* Status: working and under development

Thin ACIs don't contain any binary files, but for the most part just the manifest file and a directory skeleton.
The manifest file specifies one host type mount per package, representing the effectively available packages for the ACI.
These mountpoints can add up to a few dozen depending on the target package, and they all have to be passed to the container runtime that consumes the ACI, supplying the correct path from the host to the package's mount.

In order to make this usable, a file that can be `cat`ed into the rkt cmdline will be generated alongside the ACI when using the build script.

## Fat ACIs
* Status: working and under development

Fat ACIs contain all files that are needed to run the contained application. This is the choice if you want to move the ACI onto a system where for whichever reason the nix store outputs are not available.

## Demonstration
The following example builds the busybox ACI expression that is defined in the file [pkgs/linux/busybox.nix](pkgs/linux/busybox.nix).
In order to be available at top level, an import statement in the *default.nix* is necessary.

```
$ grep -n busybox default.nix
13:  busybox = import pkgs/linux/busybox.nix { inherit pkgs mkACI; static=false; };
14:  busyboxStatic = import pkgs/linux/busybox.nix { inherit pkgs mkACI; static=true; };
```

Now let's build, sign and run it:
```
$ nix-build -A busybox

$ ./result/postprocess.sh 
Linking /nix/store/y7dh7bfdhafaf530lih071515z8khwva-busybox/busybox-1.23.2-linux-amd64.aci into ACIs/

$ tree ACIs/
ACIs/
├── busybox-1.23.2-linux-amd64.aci -> /nix/store/y7dh7bfdhafaf530lih071515z8khwva-busybox/busybox-1.23.2-linux-amd64.aci
└── busybox-1.23.2-linux-amd64.aci.asc

$ sudo rkt run --interactive ACIs/busybox-1.23.2-linux-amd64.aci
rkt: using image from local store for image name coreos.com/rkt/stage1-coreos:0.13.0
rkt: using image from file /home/steveej/src/github/steveej/nix2aci/ACIs/busybox-1.23.2-linux-amd64.aci
rkt: signature verified:
  Stefan Junker <mail@stefanjunker.de>
  Stefan Junker <code@stefanjunker.de>
run: group "rkt" not found, will use default gid when rendering images
/ # busybox | head -n1
BusyBox v1.23.2 () multi-call binary.
```

# Tests

The test assumes nix-build to be installed.
This can be done using following the instructions [here](https://nixos.org/wiki/How_to_install_nix_in_home_(on_another_distribution)#PRoot_Installation).
Then run:

```
bash ./test.sh
```

nix2aci

nix2aci 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

nix2aci

nix2aci 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README