Crate is a containerizer for FreeBSD. Containerization is a form of OS-level virtualization of software. It can containerize any packages and/or services into a container file, and then run the container at a later time in a dedicated FreeBSD jail.
Crate containers contain everything that is needed to run the containerized software, and only need the crate executable and system functions from the kernel to run.
- graphics: X11 programs can reuse the Xorg server running on the host.
- networking: both outgoing and incoming connections can be optionally enabled for the crate, so that TCP and UDP connections can be initiated and accepted by the program running in the container. Outside TCP/UDP ports can be mapped to the ports inside crates.
- video: programs can play videos using V4L /dev/videoN devices shared with the host.
- shared folders and files: any number of host folders and files can be shared with crates, allowing them to run using persistent state.
The manpage exists but it doesn't explain much yet, it has to be expanded.
examples/ subdirectory contains a number of examples.
Working examples (only the examples listed here are verified to be working, other examples probably do not work):
- firefox.yml: you can run the firefox browser. It will run as if it was started for the first time. It will not preserve cookies or user settings across runs. You can simultaneously run any number of instances of the firefox browser, they all will run completely independently.
- chromium.yml: similarly to firefox.yml, you can create the chromium crate (chromium.crate) which will not preserve cookies, etc., just like firefox
- chromium+tor.yml: same as chromium.yml but works through the Tor network
- opera.yml: opera.crate runs, but many sites appear broken, unlike with firefox.crate and chrome.crate
- kodi.yml: kodi.crate runs but the texts aren't displayed due to missing font dependencies
- gogs.yml: runs fine, listens on the port 3100, uses the persistent database and settings stored on the host
- zeronet.yml: runs fine, listens on the port 43111, accesses zero-net network through clear-net, so far only uses the internal db (that disappears between runs)
- zeronet+tor.yml: runs fine, listens on the port 43111, accesses zero-net network through the Tor network using the dedicated Tor browser run in the container, so far only uses the internal db (that disappears between runs)
- amass.yml: runs fine
- qtox.yml: runs fine in the crate, at the moment doesn't have a persistent state
- qbittorrent.yml: runs fine, but doesn't exit when the UI is closed: qbittorrent/qBittorrent#11052
- xeyes.yml: runs fine
- gzip.yml: runs fine, it's just the
gzipexecutable
crate is in its alpha stage. Some features might not work as intended. I only started working on it in the late June 2019, so it is a very new project.
The workflow is based on two basic operations that crate supports: create and run.
createthe crate container with the command:crate crate-spec.yml(this is done once for a crate)runthe crate with the command:crate my-crate.crate(this can be done multiple times for a crate)
crate can be installed using the port sysutils/crate: cd /usr/ports/sysutils/crate && make install clean```
Unfortunately, due to the STL feature filesystem not being available in the version of the system 12.0-RELEASE-p7 used by poudriere(8), packages can't be available on FreeBSD 12, but it can be built and installed manually with the above command. Packages should be available on FreeBSD 13.
- Inbound network ports can't be accessed from the host running the crate because of this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239590 , currently they can only be accessed from other hosts (by connecting to this host on that port).
See the TODO file in the project. It will be expanded as needed.