This dockerfile provides a ready-to-go Baikal server.

For more details, see ckulka/baikal-docker (GitHub).

I follow the same version naming scheme as Baikal themselves.

The following tags support multiple architectures, e.g. amd64, arm32v7 and arm64v8.

• 0.8.0, 0.8.0-apache, apache, latest
  • 0.8.0-apache-amd64, apache-amd64
  • 0.8.0-apache-arm32v7, apache-arm32v7
  • 0.8.0-apache-arm64v8, apache-arm64v8
• 0.8.0-nginx, nginx
  • 0.8.0-nginx-amd64, nginx-amd64
  • 0.8.0-nginx-arm32v7, nginx-arm32v7
  • 0.8.0-nginx-arm64v8, nginx-arm64v8

For earlier versions all the way back to version 0.2.7, please search in the tags tab. Version 0.4.5 and older are only available for amd64.

• Where to file issues: https://github.com/ckulka/baikal-docker/issues
• Supported architectures (more info): amd64, arm32v7, arm64v8
• Image updates: PRs for ckulka/baikal-docker
• Source of this description: https://github.com/ckulka/baikal-docker

From sabre.io/baikal:

Baikal is a Cal and CardDAV server, based on sabre/dav, that includes an administrative interface for easy management.

For more information, read the main website at baikal-server.com.

Baikal is developed by Net Gusto and fruux.

The following command will start Baikal:

docker run --rm -it -p 80:80 ckulka/baikal:nginx

Alternatively, use the provided examples/docker-compose.yaml from the Git repository:

docker-compose up

You can now open http://localhost or http://host-ip in your browser and use Baikal.

The image exposes the /var/www/baikal/Specific and /var/www/baikal/config folders, which contain the persistent data. These folders should be part of a regular backup.

If you want to use local folders instead of Docker volumes, see examples/docker-compose.localvolumes.yaml to avoid file permission issues.

You can find more installation and configuration guides here:

• Multi-Arch Builds on Docker Hub
• SSL Certificate Guide
• systemd Guide
• Unraid Installation Guide

The ckulka/baikal images come in several flavors, each designed for a specific use case.

This is the defacto image, as follows the official guidelines the closest using Apache httpd.

With that being said, it's worth checking out the nginx variant as it requires fewer resources, e.g. memory, and is a lot smaller in size.

If you are unsure about what your needs are, you probably want to use this one though.

This image relies on Apache httpd and uses the official PHP image that's packaged with the Apache web server.

It also ships with HTTPS support and self-signed certificates, which can be replaced by user-provided certificates - for more details, see the SSL Certificates: Static Certificates section.

This image uses environment variables to set Apache's ServerName and ServerAlias directives to avoid Apache httpd's warnings in the logs.

The BAIKAL_SERVERNAME environment variable is used to set the global ServerName directive, e.g. dav.example.io. For more details, see Apache Core Features: ServerName Directive.

The BAIKAL_SERVERALIAS environment variable is used to set the ServerAlias directive of the VirtualHosts, e.g. dav.example.org dav.example.com. For more details, see Apache Core Features: ServerAlias Directive.

This image builds the master branch from the source repository ckulka/baikal-docker. Use at your own risk.

This image relies on nginx and uses the official nginx image.

Compared to the Apache variant, it is significantly smaller (less than half the size) and produces no warning messages out-of-the-box.