[bitnami/ghost] Release 6.30.0-debian-12-r0 (#92516)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-04-16 14:43:55 +02:00 committed by GitHub
parent 7ece66655e
commit a9f6670631
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 14 additions and 71 deletions

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-04-10T17:51:40Z" \
org.opencontainers.image.created="2026-04-16T12:07:54Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/ghost/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/ghost" \
org.opencontainers.image.title="ghost" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="6.28.0"
org.opencontainers.image.version="6.30.0"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -29,10 +29,10 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"nss-wrapper-1.1.16-0-linux-${OS_ARCH}-debian-12" \
"python-3.12.13-4-linux-${OS_ARCH}-debian-12" \
"python-3.12.13-7-linux-${OS_ARCH}-debian-12" \
"node-22.22.2-0-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"ghost-6.28.0-0-linux-${OS_ARCH}-debian-12" \
"ghost-6.30.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -51,7 +51,7 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/ghost/postunpack.sh
RUN /opt/bitnami/scripts/mysql-client/postunpack.sh
ENV APP_VERSION="6.28.0" \
ENV APP_VERSION="6.30.0" \
BITNAMI_APP_NAME="ghost" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/python/bin:/opt/bitnami/node/bin:/opt/bitnami/mysql/bin:/opt/bitnami/ghost/bin:$PATH"

View File

@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name ghost bitnami/ghost:latest
```
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/ghost/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/ghost/docker-compose.yml)
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/ghost).
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@ -116,8 +124,6 @@ The following tables list the main variables you can set.
| `GHOST_DEFAULT_PORT_NUMBER` | Default Ghost port number to enable at build time. | `2368` |
| `GHOST_DEFAULT_DATABASE_HOST` | Default database server host. | `mysql` |
When you start the Ghost image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
#### Examples
##### SMTP configuration
@ -136,70 +142,7 @@ The Bitnami Ghost Docker image from the [Bitnami Secure Images](https://go-vmwar
## Logging
The Bitnami Ghost Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs ghost
```
Or using Docker Compose:
```console
docker-compose logs ghost
```
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
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
docker stop ghost
```
Or using Docker Compose:
```console
docker-compose stop ghost
```
#### Step 2: Run the backup command
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
```console
docker run --rm -v /path/to/ghost-backups:/backups --volumes-from ghost busybox \
cp -a /bitnami/ghost /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MySQL database container:
```diff
$ docker run -d --name mysql \
...
- --volume /path/to/mysql-persistence:/bitnami/mysql \
+ --volume /path/to/mysql-backups/latest:/bitnami/mysql \
bitnami/mysql:latest
```
For the Ghost container:
```diff
$ docker run -d --name ghost \
...
- --volume /path/to/ghost-persistence:/bitnami/ghost \
+ --volume /path/to/ghost-backups/latest:/bitnami/ghost \
bitnami/ghost:latest
```
The Bitnami Ghost Docker image sends the container logs to the `stdout`. 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.
## Customize this image