Skip to content

[WIP] tools for using FreeBSD jails as lightweight containers for PaaS

License

Notifications You must be signed in to change notification settings

zenny/lightjail

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

lightjail

lightjail is a modular system for using FreeBSD jails as lightweight ephemeral containers. Projects like PaaS, CI, secure sandboxing, development environments will find it useful.

ljspawn

At the core of lightjail is the very lightweight ljspawn tool. It allows you to use FreeBSD's jail syscall without using the stock FreeBSD jail infrastructure, which was designed for persistent virtual environments, not one-off ephemeral processes. Hopefully, it's secure :-)

ljbuild

ljbuild is the overlay build script runner for lightjail. It takes care of mounting the world and the directory of what you're building (using nullfs/unionfs) and running the installation script using ljspawn. The Jailfile build script format is simple:

# Example: Jailfile for installing Ruby
# Comments start with a # symbol, like in the shell
name lang/ruby # Required. This is the directory where it will be built. MUST contain a slash (subdirectory)
version 2.1.1 # Optional, `0.0.0-<random string>` will be used by default
world 10.0-RELEASE # Techically optional, `uname -r` of the host will be used by default
from lang/common ~> 1.0 # Optional. This is the parent overlay.
                        # You can use any constraints supported by gosemver here.
copy / # Optional. Copies all files in the Jailfile's directory to the specified directory inside the overlay

#!/bin/sh
pkg install -y ruby21
pkg clean -aqy

The directory structure

There is a root directory for all lightjail related things. It MUST be read from the LIGHTJAIL_ROOT environment variable by all lj* tools, /usr/local/lj MUST be used if the variable is empty.

Under the root, there MUST be a worlds directory. Under worlds, directories MUST contain FreeBSD base system installations. The directories MUST be named with whatever version they contain (result of uname -r.) The installations MUST have ports and pkg configured.

The overlays MUST be stored under the root. Each overlay MUST be stored in a subdirectory, eg. namespace / name.

Example world installation

W=/usr/local/lj/worlds/$(uname -r)
IFACE=eth0 # your default gateway network interface, could also be vtnet0 or something
mkdir -p $W
cd /usr/src
make buildworld
make installworld DESTDIR=$W
make distribution DESTDIR=$W
cp /etc/resolv.conf $W/etc
mount -t devfs devfs $W/dev
ljspawn -f $IFACE -d $W -p '#!/bin/sh
portsnap fetch extract 
make -C/usr/ports/ports-mgmt/pkg install clean
pkg'
umount $W/dev

Running this as root should install a world to eg. /usr/local/lj/worlds/10.0-RELEASE. You don't have to do this on every server. Do it once, archive it with cpio, compress with xz, copy to all servers (with the same CPU architecture, of course) and extract there.

Requirements

  1. You must set up devfs rules:
  • sudo cp /etc/defaults/devfs.rules /etc/devfs.rules
  • sudo sysrc devfs_load_rulesets="YES"
  • sudo service devfs restart

About

[WIP] tools for using FreeBSD jails as lightweight containers for PaaS

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published