README
¶
rkt stage1-skim
A rkt flavor for running pods natively on a host. In case you need full access to the host, but don't want the application or pod cluttering up your filesystem.
WARNING
This project is experimental and unsupported. While it generally should work, and we generally will accept contributions, it may break at any given time.
Dependencies and Building
You will need Go (at least 1.6 for the versioning), and Glide
To build the stage1 flavor:
./build.sh
For your benefit, build.sh also accepts a single argument clean that will
remove all build artifacts from the build tree.
Using
Skim is based off of fly
which is an another stage1 flavor for rkt designed to run your application pod inside of
a chroot environment. Just like fly, skim can only run one executable at a time. In
addition, the executable defined in your ACI pod image, or passed via rkt run, will
need to be specified as an absolute path. This is due to the path mangling skim does
to ensure the correct binary is invoked.
Otherwise, place stage1-skim.aci into your rkt stage1 path or specify the handler
using something along the lines of --stage1-path.
Lastly, you will need to pass the following into rkt as the stage1 flavor is not signed:
--insecure-options=image
Please note, this stage1 should only be used with specially created images that are intended for this stage1. Due to its dependency on the host operating system, it should only be used on Container Linux by CoreOS.
Licensing
This code is available under the Apache-2 license, unless otherwise noted.
Directories