Portus Official Docker image
This directory contains all the resources needed to create a production-ready
Docker image for Portus.
The master branch of this repository is going to include the files needed
to build Portus from the
master branch, which is tagged as
branches are available to build Portus out of more stable branches. These
branches are going to be named using the following scheme:
Moreover, note that the deployment method has changed quite a lot:
- From 2.0 to 2.2, Portus uses Apache.
- From 2.3 onwards (including
head), Portus uses Puma.
This file contains instructions on the Puma deployment. If you want to know more
about how to deploy other versions of Portus, please refer to this file on their
SUSE's containers team cares about security, hence we made the following
- This image is running in the
productionenvironment, and because of that
SSL is enabled by default. You can disable this by setting the
PORTUS_CHECK_SSL_USAGE_ENABLEDenvironment variable to false, but we don't
- Portus is installed from an RPM package, this ensures the final image will
have only the runtime dependency; no build time dependency is ever installed.
SUSE's containers team is constantly working to automate the release process
of Portus and of this image to ensure it stays up-to-date and secure.
When deploying this image make sure to add all the required keys and
certificates at runtime instead of adding them to a Docker image.
Anatomy of the image
The image is based on openSUSE 42.2 and installs Portus using the RPM package
built by SUSE's containers team inside of the Open Build Service
top level project and subprojects (one subproject per portus branch).
This image is using Puma as the web server and it only binds to the
The init script
This Docker image has a init script which takes care of the following actions:
- Setup the database required by Portus
- Import all the
- Start Puma
The next sections will provide more details about these steps.
Portus' state is stored inside of a MariaDB database. This makes this Docker
This image has a custom
init script that takes care of configuring the external
The script will keep trying to reach the database for 90 seconds. A 5 seconds
pause is done after each failed attempt. The container will exit with an error
message if the database is not reachable.
The script will take care of the creation of the Portus database and its initial
population via the usual Rails procedures.
The database is automatically migrated whenever a new migration is introduced
by the upstream project.
Secrets and certificates
Portus requires both a SSL key and a certificate to serve its contents over
HTTPS. These files must be located in the
/certificates directory of the
container. Moreover, it's up to the deployer to set the
PORTUS_PUMA_TLS_CERT environment variables. Note that the key is also
used to sign the JWT tokens issued to authenticate all the docker clients
against the Registry.
It's also required to add the certificate of the Registry when the latter one
uses TLS to secure itself. The Registry certificate must be placed inside
init script of this image will automatically import
it if it ends with the
All logging is done to
stderr. This makes it possible to handle
the logs of this image in the usual ways.
It's possible to deploy this image using one of the existing orchestration
solutions for Docker images. You can read some examples in the
directory of Portus' source code.
Executing the crono script
Portus uses crono to handle some
background jobs. You can also execute this piece with this image. In order to do
this, you need to set the
PORTUS_INIT_COMMAND environment variable to
Here's the full list of environment variables:
Security related settings:
PORTUS_SECRET_KEY_BASE: you can generate it using
openssl rand -hex 64
PORTUS_KEY_PATH: the path of the certificate key. This is the key that
Portus will use for the authentication with your Docker registry.
PORTUS_PASSWORD: the password of the hidden
portususer. You can
generate it using
openssl rand -hex 64
PORTUS_PUMA_TLS_KEY: The TLS key to be picked by Puma.
PORTUS_PUMA_TLS_CERT: The TLS certificate to be picked by Puma.
PORTUS_CHECK_SSL_USAGE_ENABLED: Set this to
falseif you want to disable
Database releated settings (see configuring the database for details):
PORTUS_DB_ADAPTER: database type. Supported values are
mysql2. Default is
PORTUS_DB_HOST: the host running the MariaDB (or Postgres) database.
PORTUS_DB_USERNAME: the database user to be used.
PORTUS_DB_PASSWORD: the password of the database user.
PORTUS_DB_DATABASE: the name of the Portus database.
PORTUS_DB_PORT: alternative database port number.
PORTUS_DB_POOL: the number of pool connections.
PORTUS_DB_TIMEOUT: timeout value for requests.
Deployment related settings:
PORTUS_MACHINE_FQDN_VALUE: this is the fully qualified domain name of your
Portus instance (eg:
Some fine tuning for Puma:
PORTUS_PUMA_WORKERS: the amount of Puma workers to be spawned. Defaults to 1.
PORTUS_PUMA_MAX_THREADS: the maximum amount of Puma threads to be
created. Defaults to 1.
RAILS_SERVE_STATIC_FILES: set this to
trueif you want Puma to serve the
static files. Defaults to false, in which case you'd need for example NGinx
in front of this container.
Executing other commands:
PORTUS_INIT_COMMAND: you can set this environment variable with the
command that you'd like to run. For example, if you want to run crono, you
can set it to "bin/crono".
PORTUS_BACKGROUND: you can set this environment to true in order to
indicate that the process to be executed is the rails runner
bin/background.rb(that is, the background process). This is a shortcut
PORTUS_INIT_COMMAND=rails r /srv/Portus/bin/background.rb.
You can also pass further environment variables to configure Portus as