Skip to content

Upgrade Concourse#

Using the Upgrade Command#

Use the concourse upgrade command to check for and install a newer version:

1
concourse upgrade

Manual Upgrade#

To manually upgrade Concourse:

  1. Stop the server.

    bash concourse stop

  2. Back up your data. Copy the buffer_directory and database_directory to a safe location.

  3. Run the new installer. Download and execute the installer for the new version. It will detect the existing installation and upgrade in place.

    bash curl -o concourse-server.bin -L http://concoursedb.com/download/latest sh concourse-server.bin

  4. Start the server.

    bash concourse start

Docker Upgrade#

For Docker deployments, pull the new image and recreate the container:

1
2
3
4
5
6
7
docker stop concourse
docker rm concourse
docker pull cinchapi/concourse:latest
docker run -p 1717:1717 \
    -v /path/to/local/data:/data \
    --name concourse \
    cinchapi/concourse

Persistent Data

As long as you mount the same data volume (-v), your data is preserved across container recreations.

Configuration Migration#

Starting with version 0.12, Concourse prefers YAML configuration files (concourse.yaml) over the older .prefs format. Both formats are still supported, but YAML files take precedence.

If you are upgrading from a version that used .prefs files, your existing configuration continues to work. To migrate, copy your settings to concourse.yaml using the YAML format documented in Configuration.

Version Compatibility#

  • Client drivers are backward compatible with older servers.
  • Newer servers support older client driver versions through automatic cross-version translation.
  • All nodes in a distributed cluster must run the same version.