[bitnami/concourse] Release 8.0.2-debian-12-r0 (#91011)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-20 00:26:43 +01:00
committed by GitHub
parent 839b5f26cc
commit 4ea9eaf4f5
2 changed files with 9 additions and 81 deletions
+5 -5
View File
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-19T01:05:22Z" \
org.opencontainers.image.created="2026-02-19T23:15:52Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/concourse/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/concourse" \
org.opencontainers.image.title="concourse" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="8.0.1"
org.opencontainers.image.version="8.0.2"
ENV OS_ARCH="${TARGETARCH:-amd64}" \
OS_FLAVOUR="debian-12" \
@@ -27,7 +27,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"concourse-8.0.1-3-linux-${OS_ARCH}-debian-12" \
"concourse-8.0.2-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -45,9 +45,9 @@ RUN touch /.flyrc && chmod g+rwX /.flyrc
RUN update-alternatives --set iptables /usr/sbin/iptables-legacy && \
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
ENV APP_VERSION="8.0.1" \
ENV APP_VERSION="8.0.2" \
BITNAMI_APP_NAME="concourse" \
IMAGE_REVISION="4" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/concourse/bin:$PATH"
CMD [ "/opt/bitnami/concourse/bin/concourse", "--help" ]
+4 -76
View File
@@ -62,54 +62,22 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## Using `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](https://github.com/bitnami/charts/tree/main/bitnami/concourse).
## Persisting your application
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.
```console
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`](https://github.com/bitnami/containers/blob/main/bitnami/concourse/docker-compose.yml) file present in this repository:
```yaml
concourse:
...
volumes:
- /path/to/concourse-persistence:/bitnami/concourse
...
```
## Connecting to other containers
Using [Docker container networking](https://docs.docker.com/engine/userguide/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.
### Using the Command Line
#### Step 1: Create a network
```console
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.
```console
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.
## Configuration
Find how to configure Concourse in its [official documentation](https://concourse-ci.org//docs.html).
@@ -136,46 +104,6 @@ docker logs concourse
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance
### Upgrade this image
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
```console
docker pull bitnami/concourse:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker stop concourse
```
#### Step 3: Remove the currently running container
```console
docker rm -v concourse
```
#### Step 4: Run the new image
Re-create your container from the new image.
```console
docker run --name concourse bitnami/concourse:latest
```
## Using `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](https://github.com/bitnami/charts/tree/main/bitnami/concourse).
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](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.