bitnami/concourse
Bitnami container image for Concourse
100K+
Concourse is an automation system written in Go. It is most commonly used for CI/CD, and is built to scale to any kind of automation pipeline, from simple to complex.
docker run --name concourse bitnami/concourse:latest
Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options for the PostgreSQL container for a more secure deployment.
Looking to use Concourse in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
Please check the Bitnami Premium page in our partner Arrow Electronics for more information.
Dockerfile
linksLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
You can see the equivalence between the different tags by taking a look at the tags-info.yaml
file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml
.
Subscribe to project updates by watching the bitnami/containers GitHub repo.
The recommended way to get the Bitnami concourse Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/concourse:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
docker pull bitnami/concourse:[TAG]
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build
command. Remember to replace the APP
, VERSION
and OPERATING-SYSTEM
path placeholders in the example command below with the correct values.
git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the /bitnami
path. If the mounted directory is empty, it will be initialized on the first run.
docker run \
-v /path/to/concourse-persistence:/bitnami/concourse \
bitnami/concourse:latest
You can also do this with a minor change to the docker-compose.yml
file present in this repository:
concourse:
...
volumes:
- /path/to/concourse-persistence:/bitnami/concourse
...
Using Docker container networking, a different server running inside a container can easily be accessed by your application containers and vice-versa.
Containers attached to the same network can communicate with each other using the container name as the hostname.
Step 1: Create a network
docker network create concourse-network --driver bridge
Step 2: Launch the concourse container within your network
Use the --network <NETWORK>
argument to the docker run
command to attach the container to the concourse-network
network.
docker run --name concourse-node1 --network concourse-network bitnami/concourse:latest
Step 3: Run another container
We can launch another container using the same flag (--network NETWORK
) in the docker run
command. If you also set a name to your container, you will be able to use it as hostname in your network.
Find how to configure Concourse in its official documentation.
Customizable environment variables
Name | Description | Default Value |
---|---|---|
CONCOURSE_WEB_PUBLIC_DIR | Concourse web/public directory. | ${CONCOURSE_BASE_DIR}/web/public |
CONCOURSE_SESSION_SIGNING_KEY_FILE | Concourse private key for signing. | ${CONCOURSE_KEY_DIR}/session_signing_key |
CONCOURSE_TSA_HOST_KEY_FILE | Concourse private key for TSA. | ${CONCOURSE_KEY_DIR}/tsa_host_key |
CONCOURSE_TSA_HOST_PUBLIC_KEY_FILE | Concourse public key for TSA. | ${CONCOURSE_TSA_HOST_KEY_FILE}.pub |
CONCOURSE_TSA_WORKER_KEY_FILE | Concourse private key for worker. | ${CONCOURSE_KEY_DIR}/worker_key |
CONCOURSE_TSA_WORKER_PUBLIC_KEY_FILE | Concourse public key for worker. | ${CONCOURSE_TSA_WORKER_PRIVATE_KEY}.pub |
CONCOURSE_USERNAME | Concourse main local user. | user |
CONCOURSE_PASSWORD | Concourse local user password. | bitnami |
CONCOURSE_RUNTIME | Concourse runtime. | containerd |
CONCOURSE_WEB_PORT_NUMBER | Concourse Web port. | 8080 |
CONCOURSE_WEB_TSA_PORT_NUMBER | Concourse Web TSA port | 2222 |
CONCOURSE_WEB_TSA_DEBUG_PORT_NUMBER | Concourse Web Debug TSA port | 2221 |
CONCOURSE_WORKER_GARDEN_PORT_NUMBER | Concourse Worker Garden port | 7777 |
CONCOURSE_WORKER_BAGGAGECLAIM_PORT_NUMBER | Concourse worker Baggageclaim port | 7788 |
CONCOURSE_WORKER_BAGGAGECLAIM_DEBUG_PORT_NUMBER | Concourse worker Baggageclaim debug port | 7787 |
CONCOURSE_WORKER_HEALTH_PORT_NUMBER | Concourse worker healthcheck port | 8888 |
CONCOURSE_BIND_IP | Concourse bind IP | 0.0.0.0 |
CONCOURSE_TSA_BIND_IP | Concourse TSA bind IP | 127.0.0.1 |
CONCOURSE_TSA_DEBUG_BIND_IP | Concourse TSA debug bind IP | 127.0.0.1 |
CONCOURSE_EXTERNAL_URL | Concourse external URL | http://127.0.0.1 |
CONCOURSE_PEER_ADDRESS | Concourse peer address | 127.0.0.1 |
CONCOURSE_APACHE_HTTP_PORT_NUMBER | Concourse Web HTTP port, exposed via Apache with basic authentication. | 80 |
CONCOURSE_APACHE_HTTPS_PORT_NUMBER | Concourse Web HTTPS port, exposed via Apache with basic authentication. | 443 |
CONCOURSE_DATABASE_HOST | Database host address. | 127.0.0.1 |
CONCOURSE_DATABASE_PORT_NUMBER | Database host port. | 5432 |
CONCOURSE_DATABASE_NAME | Database name. | bitnami_concourse |
CONCOURSE_DATABASE_USERNAME | Database username. | bn_concourse |
CONCOURSE_DATABASE_PASSWORD | Database password. | nil |
Read-only environment variables
Name | Description | Value |
---|---|---|
CONCOURSE_BASE_DIR | Concourse installation directory. | ${BITNAMI_ROOT_DIR}/concourse |
CONCOURSE_BIN_DIR | Concourse directory for binary files. | ${CONCOURSE_BASE_DIR}/bin |
CONCOURSE_LOGS_DIR | Concourse logs directory. | ${CONCOURSE_BASE_DIR}/logs |
CONCOURSE_TMP_DIR | Concourse temporary directory. | ${CONCOURSE_BASE_DIR}/tmp |
CONCOURSE_WEB_LOG_FILE | Concourse log file for the web service. | ${CONCOURSE_LOGS_DIR}/concourse-web.log |
CONCOURSE_WEB_PID_FILE | Concourse PID file for the web service. | ${CONCOURSE_TMP_DIR}/concourse-web.pid |
CONCOURSE_WORKER_LOG_FILE | Concourse log file for the worker service. | ${CONCOURSE_LOGS_DIR}/concourse-worker.log |
CONCOURSE_WORKER_PID_FILE | Concourse PID file for the worker service. | ${CONCOURSE_TMP_DIR}/concourse-worker.pid |
CONCOURSE_KEY_DIR | Concourse keys directory. | ${CONCOURSE_BASE_DIR}/concourse-keys |
CONCOURSE_VOLUME_DIR | Concourse directory for mounted data. | ${BITNAMI_VOLUME_DIR}/concourse |
CONCOURSE_DAEMON_USER | Concourse daemon system user. | concourse |
CONCOURSE_DAEMON_GROUP | Concourse daemon system group. | concourse |
The Bitnami concourse Docker image sends the container logs to stdout
. To view the logs:
docker logs concourse
You can configure the containers logging driver using the --log-driver
option if you wish to consume the container logs differently. In the default configuration docker uses the json-file
driver.
Bitnami provides up-to-date versions of concourse, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
Step 1: Get the updated image
docker pull bitnami/concourse:latest
Step 2: Stop the running container
Stop the currently running container using the command
docker stop concourse
Step 3: Remove the currently running container
docker rm -v concourse
Step 4: Run the new image
Re-create your container from the new image.
docker run --name concourse bitnami/concourse:latest
docker-compose.yaml
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.
If you detect any issue in the docker-compose.yaml
file, feel free to report it or contribute with a fix by following our Contributing Guidelines.
We'd love for you to contribute to this container. You can request new features by creating an issue or submitting a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to fill the issue template.
Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.