Building with Docker

1. Building Docker Image

Before building the font files, we'll first need to build a Docker image. This has to be done only once. We're going to use the image name iosevka-builder here, but you can set it to whatever you want.

git clone --depth 1 https://github.com/be5invis/Iosevka.git
cd Iosevka
docker build -t iosevka-builder docker

To confirm that the docker image now exists, you can run:

docker images | grep iosevka-builder

The output should be something like this:

iosevka-builder            latest      c847d5e08886   About a minute ago   491MB

At this point, you can delete the cloned repo, because the Docker container is going to download a fresh copy of the source by default. (That is, unless you want to make the Docker container use a local copy - see below.)

cd ..
rm -rf Iosevka/

2. Building Font Files

docker run -it --rm [-e SOURCE=<SOURCE>] [-e NPM_REG=<URL>] -v $PWD:/work iosevka-builder [<BUILD_ARGS>]

Optional environment variables include:

• SOURCE - source to download (see formats below). If unset, defaults to latest release.
• NPM_REG - NPM registry mirror URL, e.g. https://mirrors.huaweicloud.com/repository/npm

SOURCE accepts several formats:

Format	Example	Meaning
ref	v34.1.0, main, abc123f	Tag, branch or commit
owner/repo@ref	you/YourIosevkaFork@v34.1.0	Tag, branch or commit from a specific fork repo
owner/repo	you/YourIosevkaFork	Latest release from a specific fork repo

For supported <BUILD_ARGS>, please refer to Customized Build.

Note that each container run will download and unpack a source tarball and install dependencies afresh. If you want to avoid re-downloading source (e.g. when iterating on a build plan) or use a local copy of the source, you'll need to override the Docker entrypoint. Check below for examples.

Examples

Default Build

docker run -it --rm -v $PWD:/work iosevka-builder

Custom Build

This will build Iosevka ss06 in all formats, ss12 TTF and ss15 webfont:

docker run -it --rm -e SOURCE=v34.1.0 -v $PWD:/work iosevka-builder contents::IosevkaSS06 ttf::IosevkaSS12 webfont::IosevkaSS15

Custom Build Plans

This example will:

• Gather build plans from myfont1.toml, myfont2.toml and myfont3.toml into a single private-build-plans.toml file.
• Build MyFont1 and MyFont2 as TTF, and MyFont3 in all formats.

cat myfont1.toml myfont2.toml myfont3.toml > private-build-plans.toml
docker run -it --rm -e SOURCE=v34.1.0 -v $PWD:/work iosevka-builder ttf::MyFont1 ttf::MyFont2 contents::MyFont3

To prepare the custom build plans, please refer to Configuring Custom Build or use the Customizer.

Using a Fork

docker run -it --rm -e SOURCE=you/YourIosevkaFork@v34.1.0 -v $PWD:/work iosevka-builder contents::Iosevka

Interactive Mode (Downloaded Source)

To keep the downloaded source between builds, override the entrypoint to get an interactive shell. /build.sh keeps track of the version used for the previous run and re-downloads only if necessary.

docker run -it --rm -v $PWD:/work --entrypoint bash iosevka-builder
$ /build.sh ttf::MyFont
# Make some changes and rebuild
$ cat myfont1.toml myfont2.toml myfont3.toml > private-build-plans.toml
$ /build.sh ttf::MyFont
# Rebuild with a different source version
$ SOURCE=v34.0.0 /build.sh ttf::MyFont
$ exit

Using Local Source

To build from a local Iosevka checkout, override the entrypoint like so:

docker run -it --rm -v /path/to/iosevka:/work --entrypoint bash iosevka-builder -c 'npm install && npm run build -- ttf::MyFont'

Interactive Mode (Local Source)

To run repeated builds from local source in interactive mode:

docker run -it --rm -v /path/to/iosevka:/work --entrypoint bash iosevka-builder
$ npm install
$ npm run build -- ttf::MyFont
$ exit