This section describes what you need to install Charliecloud and how to do so.
Note that installing and using Charliecloud can be done as a normal user with no elevated privileges, provided that user namespaces have been enabled.
We provide tarballs with a
configure script. Thus, build and install can be as
$ ./configure $ make $ sudo make install
If you don’t have sudo, you can:
Run Charliecloud directly from the build directory; add
$PATHand you are good to go, without
Install in a prefix you have write access to, e.g. in your home directory with
configure will provide a detailed report on what will be built and
installed, along with what dependencies are present and missing.
If you obtain the source code with Git, you must build
friends yourself. To do so, you will need the following. The versions in most
common distributions should be sufficient.
pip3package installer and its
This script has a few options; see its
Note that Charliecloud disables Automake’s “maintainer mode” by default, so
the build system (Makefiles,
configure, etc.) will never automatically
be rebuilt. You must run
autogen.sh manually if you need this. You can
also re-enable maintainer mode with
configure if you like, though this
is not a tested configuration.
configure has the following options in addition to the
184.108.40.206. Feature selection:
By default, all features that can be built will be built and installed. You can exclude some features with:
don’t build or install
ch-imageunprivileged builder & image manager
You can also say
--enable-FOO to fail the build if
220.127.116.11. Dependency selection:
Some dependencies can be specified as follows. Note that
is not supported; use the feature selectors above.
Shebang line to use for Python scripts. Default:
sphinx-buildexecutable. Default: the
sphinx-buildfound first in
Path to Python used by
sphinx-build. Default: shebang of
18.104.22.168. Less strict build:
Please do not use this option routinely, as that hides bugs that we cannot find otherwise.
By default, Charliecloud builds with
-Werror. The principle here is that we prefer diagnostics that are as noisy
as practical, so that problems are identified early and we can fix them. We
-Werror unless there is a specific reason to turn it off. For
example, this approach identified a buggy
configure test (issue #798).
Many others recommend the opposite. For example, Gentoo’s “Common mistakes”
guide advises against
-Werror because it causes breakage that is
“random” and “without purpose”. There is a well-known blog post
from Flameeyes that recommends
-Werror be off by default and used by
developers and testers only.
In our opinion, for Charliecloud, these warnings are most likely the result of
real bugs and shouldn’t be hidden (i.e., they are neither random nor without
purpose). Our code should have no warnings, regardless of compiler, and any
spurious warnings should be silenced individually. We do not have the
resources to test with a wide variety of compilers, so enabling
-Werror only for development and testing, as recommended by others,
means that we miss potentially important diagnostics — people typically do not
pay attention to warnings, only errors.
That said, we recognize that packagers and end users just want to build the
code with a minimum of hassle. Thus, we provide the
Don’t hesitate to use it. But if you do, we would very much appreciate if you:
File a bug explaining why! We’ll fix it.
Remove it from your package or procedure once we fix that bug.
22.214.171.124. Disable bundled Lark package:
This option is minimally supported and not recommended. Use only if you really know what you are doing.
Charliecloud uses the Python package Lark for parsing Dockerfiles and image references. Because this package is developed rapidly, and recent versions have important features and bug fixes not yet available in common distributions, we bundle the package with Charliecloud.
If you prefer a separately-installed Lark, either via system packages or
pip, you can use
./configure --disable-bundled-lark. This
excludes the bundled Lark from being installed or placed in
tarballs. It does not remove the bundled Lark from the source directory; if
you run from the source directory (i.e., without installing), the bundled Lark
will be used if present regardless of this option.
Bundled Lark is included in the tarballs we distribute. You can remove it and
./autogen.sh --rm-lark --no-lark. If
you are starting from a Git checkout, bundled Lark is installed by default by
./autogen.sh, but you can prevent this with
The main use case for these options is to support package maintainers. If this is you and does not meet your needs, please get in touch with us and we will help.
Charliecloud is also available using a variety of distribution and third-party package managers.
Maintained by us:
Maintained by others:
Note that Charliecloud development moves quickly, so double-check that packages have the version and features you need.
Pull requests and other collaboration to improve the packaging situation are particularly welcome!
Charliecloud’s philosophy on dependencies is that they should be (1) minimal and (2) granular. For any given feature, we try to implement it with the minimum set of dependencies, and in any given environment, we try to make the maximum set of features available.
This section documents Charliecloud’s dependencies in detail. Do you need to
read it? If you are installing Charliecloud on the same system where it will
be used, probably not.
configure will issue a report saying what will
and won’t work. Otherwise, it may be useful to gain an understanding of what
to expect when deploying Charliecloud.
Note that we do not rigorously track dependency versions. We update the minimum versions stated below as we encounter problems, but they are not tight bounds and may be out of date. It is worth trying even if your version is documented to be too old. Please let us know any success or failure reports.
Finally, the run-time dependencies are lazy; specific features just try to use their dependencies and fail if there’s a problem, hopefully with a useful error message. In other words, there’s no version checking or whatnot that will keep you from using a feature unless it truly doesn’t work in your environment.
Charliecloud’s fundamental principle of a workflow that is fully unprivileged end-to-end requires unprivileged user namespaces. In order to enable them, you need a vaguely recent Linux kernel with the feature compiled in and active.
Some distributions need configuration changes. For example:
Debian Stretch needs sysctl
RHEL/CentOS 7.4 and 7.5 need both a kernel command line option and a sysctl. RHEL/CentOS 7.6 and up need only the sysctl. Note that Docker does not work with user namespaces, so skip step 4 of the Red Hat instructions, i.e., don’t add
--userns-remapto the Docker configuration (see issue #97).
Note: User namespaces always fail in a chroot with
configure detects that it’s in a chroot, it will print a warning in
its report. One common scenario where this comes up is packaging, where builds
often happen in a chroot. However, like all the run-time
tests, this is informational only and does not affect the build.
Charliecloud should work on any architecture supported by the Linux kernel, and we have run Charliecloud containers on x86-64, ARM, and Power. However, it is currently tested only on x86_64 and ARM.
Most builders are also fairly portable; e.g., see Docker’s supported platforms.
This section is a comprehensive listing of the specific dependencies and
versions by feature group. It is autogenerated from the definitive source,
Listed versions are minimums, with the caveats above. Everything needs a POSIX shell and utilities.
The next section contains notes about some of the dependencies.
126.96.36.199. Building Charliecloud¶
lark.py under source dir
“docutils” module ≥ 0.14
“sphinx-rtd-theme” module ≥ 0.2.4
188.8.131.52. Building images via our wrappers¶
Buildah ≥ 1.11.2
Python shebang line
Python in shebang ≥ 3.6
“requests” module ≥ 2.6.0
Docker ≥ 17.03
184.108.40.206. Managing container images¶
build from Dockerfile with
at least one builder
access to an image repository
pack images from builder storage to tarball:
at least one builder
pack images from builder storage to SquashFS:
at least one builder
Note: Pulling/pushing images from/to a repository is currently done using the builder directly.
220.127.116.11. Running containers¶
unpack image tarballs:
ch-umount SquashFS images:
SquashFUSE ≥ 0.1.100
inject nVidia GPU libraries:
nVidia libraries & executables present
18.104.22.168. Test suite¶
test suite enabled
Bats ≥ 0.4.0
Bash ≥ 4.1
recommended tests with tarballs:
any builder above
access to Docker Hub or mirror
pack images with tar
unpack images with tar
recommended tests with SquashFS:
recommended tests with tar
pack images with SquashFS
mount/unmount SquashFS images
complete test suite:
recommended tests with SquashFS
ShellCheck ≥ 0.6.0
This section describes additional details we have learned about some of the dependencies. Note that most of these are optional. It is in alphabetical order by dependency.
When Bash is needed, it’s because:
Shell scripting is a lot easier in Bash than POSIX shell, so we use it for scripts applicable in contexts where it’s very likely Bash is already available.
It is required by our testing framework, Bats.
Bats (“Bash Automated Testing System”) is a test framework for tests written as Bash shell scripts.
Upstream Bats is unmaintained, but widely available. Both version 0.4.0, which tends to be in distributions, and upstream master branch (commit 0360811) should work. There is a maintained fork called Bats-core, but the test suite currently does not pass with it; see issue #582. Patches welcome!
Charliecloud uses Buildah’s “rootless” mode and
storage configuration for a fully unprivileged workflow with no sudo and no
setuid binaries. Note that in this mode, images in Buildah internal storage
will have all user and group ownership flattened to UID/GID 0.
If you prefer a privileged workflow, Charliecloud can also use Buildah with
newgidmap. This will not remap
To configure Buildah in rootless mode, make sure your config files are in
~/.config/containers and they are correct. Particularly if your system
also has configuration in
/etc/containers, problems can be very hard
22.214.171.124. C compiler¶
We test with GCC. Core team members use whatever version comes with their distribution.
In principle, any C99 compiler should work. Please let us know any success or failure reports.
icc is not supported because it links extra shared libraries
that our test suite can’t deal with. See PR #481.
126.96.36.199.1. Security implications of Docker¶
Because Docker (a) makes installing random crap from the internet really easy and (b) is easy to deploy insecurely, you should take care. Some of the implications are below. This list should not be considered comprehensive nor a substitute for appropriate expertise; adhere to your moral and institutional responsibilities.
Docker equals root. Anyone who can run the
dockercommand or interact with the Docker daemon can trivially escalate to root. This is considered a feature.
For this reason, don’t create the
dockergroup, as this will allow passwordless, unlogged escalation for anyone in the group. Our scripts expect to run Docker as
Also, Docker runs container processes as root by default. In addition to being poor hygiene, this can be an escalation path, e.g. if you bind-mount host directories.
Docker alters your network configuration. To see what it did:
$ ifconfig # note docker0 interface $ brctl show # note docker0 bridge $ route -n
Docker installs services. If you don’t want the Docker service starting automatically at boot, e.g.:
$ systemctl is-enabled docker enabled $ systemctl disable docker $ systemctl is-enabled docker disabled
188.8.131.52.2. Configuring for a proxy¶
By default, Docker does not work if you have a proxy, and it fails in two different ways.
The first problem is that Docker itself must be told to use a proxy. This manifests as:
$ sudo docker run hello-world Unable to find image 'hello-world:latest' locally Pulling repository hello-world Get https://index.docker.io/v1/repositories/library/hello-world/images: dial tcp 184.108.40.206:443: connection refused
If you have a systemd system, the Docker documentation explains how to
configure this. If you don’t have a systemd system, then
/etc/default/docker might be the place to go?
The second problem is that programs executed during build (
instructions) need to know about the proxy as well. This manifests as images
failing to build because they can’t download stuff from the internet.
The fix is usually to set the proxy variables in your environment, e.g.:
export HTTP_PROXY=http://proxy.example.com:8088 export http_proxy=$HTTP_PROXY export HTTPS_PROXY=$HTTP_PROXY export https_proxy=$HTTP_PROXY export ALL_PROXY=$HTTP_PROXY export all_proxy=$HTTP_PROXY export NO_PROXY='localhost,127.0.0.1,.example.com' export no_proxy=$NO_PROXY
You also need to teach
sudo to retain them. Add the following to
Defaults env_keep+="HTTP_PROXY http_proxy HTTPS_PROXY https_proxy ALL_PROXY all_proxy NO_PROXY no_proxy"
Because different programs use different subsets of these variables, and to avoid a situation where some things work and others don’t, the Charliecloud test suite will fail if some but not all of the above variables are set.
220.127.116.11. image repository access¶
FROM instructions in Dockerfiles and image pushing/pulling require
access to an image repository and configuring the builder for that repository.
We use Python for scripts that would be really hard to do in Bash, when we think Python is likely to be available.
ShellCheck is a very thorough and capable linter for shell scripts. In order to pass the full test suite, all the shell scripts need to pass ShellCheck.
While it is widely available in distributions, the packaged version is usually too old. Building from source is tricky because it’s a Haskell program, which isn’t a widely available tool chain. Fortunately, the developers provide pre-compiled static binaries on their GitHub page.
We use Sphinx to build the documentation; the theme is sphinx-rtd-theme.
Minimum versions are listed above. Note that while anything greater than the minimum should yield readable documentation, we don’t test quality with anything other than what we use to build the website, which is usually but not always the most recent version available on PyPI.
If you’re on Debian Stretch or some version of Ubuntu, installing with
pip3 will silently install into
~/.local, leaving the
sphinx-build binary in
~/.local/bin, which is often not on
your path. One workaround (untested) is to run
pip3 as root, which
violates principle of least privilege. A better workaround, assuming you can
/usr/local, is to add the undocumented and non-standard
--system argument to install in
/usr/local instead. (This
pip behavior.) See Debian bugs 725848 and 820856.
The SquashFS workflow requires SquashFS Tools and/or SquashFUSE. Note that distribution packages of SquashFUSE often provide only the “high level” executables; the “low level” executables have better performance. These can be installed from source on any distribution.
18.104.22.168. sudo, generic¶
Privilege escalation via sudo is used in the test suite to:
Prepare fixture directories for testing filesystem permissions enforcement.
ch-run’s behavior under different ownership scenarios.
(Note that Charliecloud also uses
sudo docker; see above.)
Wget is used to demonstrate building an image without a builder (the main test image used to exercise Charliecloud itself).
This section explains how to create and use a single-node virtual machine with Charliecloud and all three builders pre-installed. This lets you use Charliecloud on Macs and Windows, and/or obtain a pre-configured Charliecloud environment without installing anything.
You can use this CentOS VM either with Vagrant or with VirtualBox alone. Various settings are specified, but in most cases we have not done any particular tuning, so use your judgement, and feedback is welcome.
These instructions provide for an SSH server in the virtual machine guest that is accessible to anyone logged into the host. It is your responsibility to ensure this is safe and compliant with your organization’s policies, or modify the procedure accordingly.
This procedure imports a
.ova file into VirtualBox and walks you
through logging in and running a brief Hello World in Charliecloud. You will
act as user
charlie, who has passwordless
The Charliecloud developers do not distribute a
.ova file. You will
need to get it from your site, a third party, or build it yourself with
Vagrant using the instructions in the Contributor’s guide.
Prerequisite: Installed and working VirtualBox. (You do not need Vagrant to
.ova, only to create it.)
22.214.171.124. Configure VirtualBox¶
Set Preferences → Proxy if needed at your site.
126.96.36.199. Import the appliance¶
charliecloud_centos7.ova, or whatever your site has called it.
File → Import appliance. Choose
charliecloud_centos7.ovaand click Continue.
Review the settings.
CPU should match the number of cores in your system.
RAM should be reasonable. Anywhere from 2GiB to half your system RAM will probably work.
Tick Reinitialize the MAC address of all network cards.
Verify that the appliance’s port forwarding is acceptable to you and your site: Details → Network → Adapter 1 → Advanced → Port Forwarding.
188.8.131.52. Log in and try Charliecloud¶
Start the VM by clicking the green arrow.
Wait for it to boot.
Click on the console window, where user
charlieis logged in. If the VM “captures” your mouse pointer, type the key combination listed in the lower-right corner of the window to release it. You can avoid capture by clicking the title bar instead of window content.
Change your password. You must use
sudobecause you have passwordless
sudobut don’t know your password.
$ sudo passwd charlie
SSH (from terminal on the host) into the VM using the password you just set. Accessing the VM using SSH rather than the console is generally more pleasant, because you have a nice terminal with native copy-and-paste, etc.
$ ssh -p 2222 charlie@localhost
Build and run a container:
$ ch-build -t hello -f /usr/local/src/charliecloud/examples/serial/hello \ /usr/local/src/charliecloud $ ch-builder2tar hello /var/tmp 57M /var/tmp/hello.tar.gz $ ch-tar2dir /var/tmp/hello.tar.gz /var/tmp creating new image /var/tmp/hello /var/tmp/hello unpacked ok $ cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) $ ch-run /var/tmp/hello -- /bin/bash > cat /etc/debian_version 8.9 > exit
Congratulations! You’ve successfully used Charliecloud. Now all of your wildest dreams will come true.
Shut down the VM at your leisure.
Possible next steps:
This procedure builds and provisions an idiomatic Vagrant virtual machine. You
should also read the Vagrantfile in
proceeding. This contains the specific details on build and provisioning,
which are not repeated here.
Prerequisite: You already know how to use Vagrant.
184.108.40.206. Caveats and gotchas¶
In no particular order:
While Vagrant supports a wide variety of host and virtual machine providers, this procedure is tested only on VirtualBox on a Mac. Current Vagrant versions should work, but we don’t track specifically which ones. (Anyone who wants to help us broaden this support, please get in touch.)
Switching between proxy and no-proxy environments is not currently supported. If you have a mixed environment (e.g. laptops that travel between a corporate network and the wild), you may want to provide two separate images.
Provisioning is not idempotent. Running the provisioners again will have undefined results.
The documentation is not built. Use the web documentation instead of man pages.
Only the most recent release of Charliecloud is supported.
220.127.116.11. Install Vagrant and plugins¶
You can install VirtualBox and Vagrant either manually using website downloads or with Homebrew:
$ brew cask install virtualbox virtualbox-extension-pack vagrant
$ vagrant version Installed Version: 2.1.2 Latest Version: 2.1.2 You're running an up-to-date version of Vagrant!
Then, install the needed plugins:
$ vagrant plugin install vagrant-disksize \ vagrant-proxyconf \ vagrant-reload \ vagrant-vbguest
18.104.22.168. Build and provision¶
To build the VM and install Docker, Charliecloud, etc.:
$ cd packaging/vagrant $ vagrant up
By default, this uses the newest release of Charliecloud. If you want
something different, set the
CH_VERSION variable, e.g.:
$ CH_VERSION=v0.10 vagrant up $ CH_VERSION=master vagrant up
Then, optionally run the Charliecloud tests:
$ vagrant provision --provision-with=test
This runs the Charliecloud test suite in standard scope.
Note that the test output does not have a TTY, so you will not have the tidy checkmarks. The last test printed is the last one that completed, not the one currently running.
If the tests don’t pass, that’s a bug. Please report it!
Now you can
vagrant ssh and do all the usual Vagrant stuff.