ppc64le/ghost
Publish by web and email newsletter, with member signups and subscription payments.
100K+
Note: this is the "per-architecture" repository for the ppc64le
builds of the ghost
official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.
Maintained by:
the Docker Community
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile
linksWhere to file issues:
https://github.com/docker-library/ghost/issues
Supported architectures: (more info)amd64
, arm32v6
, arm32v7
, arm64v8
, ppc64le
, s390x
Published image artifact details:
repo-info repo's repos/ghost/
directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/ghost
label
official-images repo's library/ghost
file (history)
Source of this description:
docs repo's ghost/
directory (history)
Ghost is an independent platform for publishing online by web and email newsletter. It has user signups, gated access and subscription payments built-in (with Stripe) to allow you to build a direct relationship with your audience. It's fast, user-friendly, and runs on Node.js & MySQL8.
This will start a Ghost development instance listening on the default Ghost port of 2368.
$ docker run -d --name some-ghost -e NODE_ENV=development ppc64le/ghost
If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://localhost:3001 -p 3001:2368 ppc64le/ghost
If all goes well, you'll be able to access your new site on http://localhost:3001
and http://localhost:3001/ghost
to access Ghost Admin (or http://host-ip:3001
and http://host-ip:3001/ghost
, respectively).
You will want to ensure you are running the latest minor version of Ghost before upgrading major versions. Otherwise, you may run into database errors.
For upgrading your Ghost container you will want to mount your data to the appropriate path in the predecessor container (see below): import your content from the admin panel, stop the container, and then re-mount your content to the successor container you are upgrading into; you can then export your content from the admin panel.
Mount your existing content. In this example we also use the Alpine Linux based image.
$ docker run -d \
--name some-ghost \
-e NODE_ENV=development \
-e database__connection__filename='/var/lib/ghost/content/data/ghost.db' \
-p 3001:2368 \
-v /path/to/ghost/blog:/var/lib/ghost/content \
ppc64le/ghost:alpine
Note: database__connection__filename
is only valid in development mode and is the location for the SQLite database file. If using development mode, it should be set to a writeable path within a persistent folder (bind mount or volume). It is not available in production mode because an external MySQL server is required (see the Docker Compose example below).
Alternatively you can use a named docker volume instead of a direct host path for /var/lib/ghost/content
:
$ docker run -d \
--name some-ghost \
-e NODE_ENV=development \
-e database__connection__filename='/var/lib/ghost/content/data/ghost.db' \
-p 3001:2368 \
-v some-ghost-data:/var/lib/ghost/content \
ppc64le/ghost
All Ghost configuration parameters (such as url
) can be specified via environment variables. See the Ghost documentation for details about what configuration is allowed and how to convert a nested configuration key into the appropriate environment variable name:
$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://some-ghost.example.com ppc64le/ghost
(There are further configuration examples in the stack.yml
listed below.)
When opening a ticket at https://github.com/TryGhost/Ghost/issues it becomes necessary to know the version of Node.js in use:
$ docker exec <container-id> node --version
[node version output]
While the Docker images do have Ghost-CLI available and do use some of its commands to set up the base Ghost image, many of the other Ghost-CLI commands won't work correctly, and really aren't designed/intended to. For more info see docker-library/ghost#156 (comment)
To run Ghost for production you'll also need to be running with MySQL 8, https, and a reverse proxy configured with appropriate X-Forwarded-For
, X-Forwarded-Host
, and X-Forwarded-Proto
(https
) headers.
The following example demonstrates some of the necessary configuration for running with MySQL. For more detail, see Ghost's "Configuration options" documentation.
docker-compose
or docker stack deploy
Example docker-compose.yml
for ghost
:
version: '3.1'
services:
ghost:
image: ghost:5-alpine
restart: always
ports:
- 8080:2368
environment:
# see https://ghost.org/docs/config/#configuration-options
database__client: mysql
database__connection__host: db
database__connection__user: root
database__connection__password: example
database__connection__database: ghost
# this url value is just an example, and is likely wrong for your environment!
url: http://localhost:8080
# contrary to the default mentioned in the linked documentation, this image defaults to NODE_ENV=production (so development mode needs to be explicitly specified if desired)
#NODE_ENV: development
volumes:
- ghost:/var/lib/ghost/content
db:
image: mysql:8.0
restart: always
environment:
MYSQL_ROOT_PASSWORD: example
volumes:
- db:/var/lib/mysql
volumes:
ghost:
db:
Run docker stack deploy -c stack.yml ghost
(or docker compose -f stack.yml up
), wait for it to initialize completely, and visit http://swarm-ip:8080
, http://localhost:8080
, or http://host-ip:8080
(as appropriate).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository's ghost/
directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
docker pull ppc64le/ghost