Public | Automated Build

Last pushed: 19 hours ago
Short Description
Docker image for creating static sites from Asciidoc files using Jekyll and AsciiDoctor.
Full Description

= Docker image: boekhoff/jekyll-asciidoc
:link-alpinelinux:[Alpine Linux]
:link-gitlab-pages:[GitLab pages]
:link-gitlab-runner:[GitLab runner]
:link-use-jekyll-asciidoc-for-gitlab-pages:[documentation in the README of jekyll-asciidoc]
:link-install-runner-using-docker:[installation guide on GitLab]

This Git repository contains Dockerfiles for automated builds of Docker images
that are hosted as {link-image} on {link-dockerhub}.

The images are equipped with software for creating static sites from Asciidoc
files using {link-jekyll} and {link-asciidoctor}.

== Tags (+ installed software)

The {link-image}-images are build upon Jekyll's official Docker image
Changes in the following DockerHub repositories trigger an automated build of
the images:

The tags used by {link-image} resemble the version of the installed[jekyll-asciidoc] release.

== Usage

The Docker images are hosted as {link-image} on {link-dockerhub}.
Thus, you can pull an image by using the following terminal command:


.Command to pull the latest image from DockerHub.

docker pull boekhoff/jekyll-asciidoc

=== Use image for GitLab-CI runner

If you store the sources for a webpage on {link-gitlab} and you want to deploy
it to {link-gitlab-pages}, you can easily make use of shared runners provided
by GitLab (see the {link-use-jekyll-asciidoc-for-gitlab-pages}).
If shared runners are to slow and/or you don't want to install all dependencies
each time you run a build, you can use {link-image} to set up a
{link-gitlab-runner} on your own machine.
The advantage is that {link-image} is already equipped with (all) dependencies
required to build webpages from Asciidoc content.

The following section shows you how to setup a {link-gitlab-runner} in a
{link-docker}-container that in addition uses Docker (with a container from the
lastest image of {link-image}) as an executor.
Also refer to the {link-install-runner-using-docker} for additional options.

. Start a GitLab container using the official Docker image for GitLab runners
Here I use the {link-alpinelinux} based image because of its small footprint.


sudo docker run \
-d \
--name myRunner \
--restart always \
-v /srv/gitlab-runner/config:/etc/gitlab-runner \
-v /var/run/docker.sock:/var/run/docker.sock \


. Open a shell to the running container and start the runner configuration:


sudo docker exec \
-ti \
myRunner \

gitlab-runner register

. Follow the installation instructions.
This example uses settings for a project hosted on {link-gitlab}.
Therefore the gitlab-ci coordinator URL is


Please enter the gitlab-ci coordinator URL (e.g.

Please enter the gitlab-ci token for this runner:
[FIXME: Enter the 'Runner token' from your project settings.]

Please enter the gitlab-ci description for this runner:
[############]: Runner on machine ABC in office XYZ

Please enter the gitlab-ci tags for this runner (comma separated):
Registering runner... succeeded runner=[########]

Please enter the executor: docker+machine, docker-ssh+machine, docker, docker-ssh, parallels, shell, ssh, virtualbox:

Please enter the default Docker image (eg. ruby:2.1):


. DONE. The configuration of the runner is stored in:

Docker Pull Command

Comments (0)