Skip to content

Versions

Container images are published using a versioning system called CalVer. This section explains how the CalVer format works, how to use these versions in your Docker Compose setup, and where to find the container images across different container registries.

Where to Find Container Images

You can find the container images hosted on popular container registries. Here are links, which will list the available versions & commands to pull down the images.

Each registry hosts the same images, tagged with their CalVer versions.

What is CalVer?

CalVer stands for "Calendar Versioning". It’s a simple, easy-to-understand versioning format designed to help you know exactly when an image was created and if there have been any updates to it.

CalVer Format

YYYY.MM.DD-R
  • YYYY - The year the image was published.
  • MM - The month of publication.
  • DD - The day the image was created.
  • R - The revision number for that day. If changes are made to the image on the same day, this number increases.

Example

2024.02.03
  • 2024 - Published in the year 2024
  • 02 - In February
  • 03 - On the 3rd day of the month

If the image was updated later the same day, it would be:

2024.02.03-2

This system makes it easy to track when an image was last updated and if any quick fixes or patches were applied on the same day.

Using CalVer Versions in Docker Compose

To use a specific container image version in your compose.yml, you’ll reference the CalVer tag like this:

services:
  mangosd:
    image: ghcr.io/thoriumlxc/cmangos-classic:2025.01.01
    # Additional environment variables or configurations can go here

In this example:

  • ghcr.io is the container registry, which is where the container image is downloaded from.
  • thoriumlxc/cmangos-classic is the organization and repository name.
  • 2025.01.01 is the specific CalVer version tag.

Using a specific CalVer version is recommended for stability, so you always know exactly which version is running.