Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-30 14:57:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/ghost] Release 6.19.3-debian-12-r0 (#91137)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-26 23:30:00 +01:00
committed by GitHub
parent 4fbdc28c6b
commit 30499c3a5e
2 changed files with 33 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
bitnami/ghost/6/debian-12/Dockerfile
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-20T17:46:55Z" \
org.opencontainers.image.created="2026-02-26T21:54:51Z" \
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.19.2"
org.opencontainers.image.version="6.19.3"
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.12-17-linux-${OS_ARCH}-debian-12" \
"python-3.12.12-22-linux-${OS_ARCH}-debian-12" \
"node-22.22.0-1-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"ghost-6.19.2-0-linux-${OS_ARCH}-debian-12" \
"ghost-6.19.3-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.19.2" \
ENV APP_VERSION="6.19.3" \
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"

54
bitnami/ghost/README.md
View File

@@ -1,13 +1,11 @@
# Bitnami Secure Image for Ghost
## What is Ghost?
> Ghost is an open source publishing platform designed to create blogs, magazines, and news sites. It includes a simple markdown editor with preview, theming, and SEO built-in to simplify editing.
[Overview of Ghost](https://ghost.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
## <a id="tl-dr"></a> TL;DR
```console
docker run --name ghost bitnami/ghost:latest
@@ -16,7 +14,7 @@ docker run --name ghost bitnami/ghost: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 in the [Environment Variables](#environment-variables) section for a more secure d
eployment.
## Why use Bitnami Secure Images?
## <a id="why-use-bitnami-secure-images"></a> 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?
@@ -33,19 +31,19 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## How to deploy Ghost in Kubernetes?
## <a id="how-to-deploy-in-kubernetes"></a> How to deploy Ghost in Kubernetes?
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Ghost Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/ghost).
## Why use a non-root container?
## <a id="why-non-root"></a> Why use a non-root container?
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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## Supported tags and respective `Dockerfile` links
## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## Get this image
## <a id="get-this-image"></a> Get this image
The recommended way to get the Bitnami Ghost Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/ghost).
@@ -67,15 +65,15 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## How to use this image
## <a id="how-to-use-this-image"></a> How to use this image
Ghost requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MySQL](https://github.com/bitnami/containers/tree/main/bitnami/mysql) for the database requirements.
### Run the application using Docker Compose
### <a id="run-the-application-using-docker-compose"></a> Run the application using Docker Compose
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).
## Persisting your application
## <a id="persisting-your-application"></a> 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.
@@ -85,11 +83,15 @@ The above examples define the Docker volumes named `mysql_data` and `ghost_data`
To avoid inadvertent removal of volumes, you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Configuration
## <a id="configuration"></a> Configuration
### Environment variables
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -147,13 +149,13 @@ The `GHOST_SMTP_*` environment variables allows you configure the SMTP settings
The Bitnami Ghost container supports connecting the Ghost application to an external database. In case the database already contains data from a previous Ghost installation, you need to set the variable `GHOST_SKIP_BOOTSTRAP` to `yes`. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting `GHOST_SKIP_BOOTSTRAP` to `yes`, values for environment variables such as `GHOST_USERNAME`, `GHOST_PASSWORD` or `GHOST_EMAIL` will be ignored.
### FIPS configuration in Bitnami Secure Images
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
The Bitnami Ghost Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## Logging
## <a id="logging"></a> Logging
The Bitnami Ghost Docker image sends the container logs to `stdout`. To view the logs:
@@ -169,9 +171,9 @@ 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
## <a id="maintenance"></a> Maintenance
### Backing up your container
### <a id="backing-up-your-container"></a> Backing up your container
To backup your data, configuration and logs, follow these simple steps:
@@ -196,7 +198,7 @@ docker run --rm -v /path/to/ghost-backups:/backups --volumes-from ghost busybox
cp -a /bitnami/ghost /backups/latest
```
### Restoring a backup
### <a id="restoring-a-backup"></a> Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
@@ -220,17 +222,17 @@ For the Ghost container:
bitnami/ghost:latest
```
## Customize this image
## <a id="customize-this-image"></a> Customize this image
The Bitnami Ghost Docker image is designed to be extended so it can be used as the base image for your custom web applications.
### Extend this image
### <a id="extend-this-image"></a> Extend this image
To do so, create your own image using a Dockerfile with the format below:
```Dockerfile
FROM bitnami/ghost
## Put your customizations below
## <a id="put-your-customizations-below"></a> Put your customizations below
...
```
@@ -239,7 +241,7 @@ This example shows how to install the [Storage Adapter for S3](https://github.co
```Dockerfile
FROM bitnami/ghost:latest
## Change user to perform privileged actions
## <a id="change-user-to-perform-privileged-actions"></a> Change user to perform privileged actions
USER root
COPY post_ghost_config.sh /
@@ -253,7 +255,7 @@ ENV AWS_ACCESS_KEY_ID="AWS_ACCESS_KEY_ID" \
AWS_REGION="AWS_REGION" \
AWS_BUCKET="AWS_BUCKET"
## Revert to the original non-root user
## <a id="revert-to-the-original-non-root-user"></a> Revert to the original non-root user
USER 1001
RUN cd /bitnami/ghost \
@@ -280,7 +282,7 @@ jq -r --arg keyId $AWS_ACCESS_KEY_ID --arg accessKey $AWS_ACCESS_SECRET_KEY --ar
Finally, build the container and set the required environment variables to configure the adapter.
## Notable Changes
## <a id="notable-changes"></a> Notable Changes
### 3.42.5-debian-10-r67 and 4.8.4-debian-10-r7
@@ -292,7 +294,7 @@ Finally, build the container and set the required environment variables to confi
- The ghost container has been migrated to a non-root container approach. Previously the container run as `root` user and the ghost daemon was started as `ghost` user. From now own, both the container and the ghost daemon run as user `1001`. As a consequence, the configuration files are writable by the user running the ghost process.
## License
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.