Supported tags and respective
Kratos Docker images come in two different flavors, one with and one
without SQLite support. All Docker images with the postfix
kratos:<version>-sqlite in the tag are compiled with embed SQLite support and
uses libmusl. All Docker images (
kratos:<version>) without the postfix
-sqlite are compiled without SQLite support and therefore also don't include
If you don't make use of the embedded SQLite support we recommend to use the Docker images without SQLite support as they are smaller in size, include fewer libraries and therefore have a smaller attack surface.
In order to make the provided Docker images as useful as possible they can be configured through a set of supported Environment variables. In addition the default configuration directory can be bound to a directory of choice to make it simple to pass in your own configuration files.
This environment variable allows you to specify the database source name. As the
DSN normally consists of the url to the database system and the credentials to
access the database it is recommended to specify the
DSN using a Environment
docker run -e DSN="memory" oryd/kratos:latest
This environment variable allows you to specify the secret used to sign and verify signatures and encrypt things:
docker run -e SECRETS_DEFAULT="CHANGE-ME" oryd/kratos:v0.4.3-alpha.1
If the file
$HOME/.kratos.yaml exists, it will be used as the configuration
file. The provided Kratos Docker images currently do not include a default
configuration file, but make it easy to pass in your own configuration file(s)
by either binding a local directory or by creating your own custom Docker Image
and adding the configuration file(s) to the custom image.
Example: In this example we start the standard Docker container with SQLite support and use the quickstart email-password example configuration files by bind mounting the local directory. This example assumes that you checked out the Kratos Git repo and execute the Docker command in the Kratos Git repo directory:
In general we only recommend this approach for local development.
You can create your own, custom Kratos Docker images which embeds your configuration files by simply using the official Kratos Docker images as the Base Image and just adding your configuration file(s) as shown in the example below:
Below you find different examples how to use the official Kratos Docker images.