Supported tags and respective
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
How to use this image
This will start a Ghost instance listening on the default Ghost port of 2368.
$ docker run -d --name some-ghost 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 -p 3001:2368 ghost
Then, access it via
http://host-ip:3001 in a browser.
Mount your existing content. In this example we also use the Alpine base image.
$ docker run -d --name some-ghost -p 3001:2368 -v /path/to/ghost/blog:/var/lib/ghost/content ghost:1-alpine
$ docker run -d --name some-ghost -p 3001:2368 -v /path/to/ghost/blog:/var/lib/ghost ghost:0.11-alpine
If you want to run Ghost 0.11.xx, be aware of the container's path difference:
- Ghost 1.x.x is:
- Ghost 0.11.x is:
This Docker image for Ghost uses SQLite. There is nothing special to configure.
Alternatively you can use a data container that has a volume that points to
/var/lib/ghost/content (or /var/lib/ghost for 0.11.x) and then reference it:
$ docker run -d --name some-ghost --volumes-from some-ghost-data ghost
What is the Node.js version?
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 v6.11.2
docker stack deploy or
# by default, the Ghost image will use SQLite (and thus requires no separate database container) # we have used MySQL here merely for demonstration purposes (especially environment-variable-based configuration) version: '3.1' services: ghost: image: ghost:1-alpine restart: always ports: - 8080:2368 environment: # see https://docs.ghost.org/docs/config#section-running-ghost-with-config-env-variables database__client: mysql database__connection__host: db database__connection__user: root database__connection__password: example database__connection__database: ghost db: image: mysql:5.7 restart: always environment: MYSQL_ROOT_PASSWORD: example
docker stack deploy -c stack.yml ghost (or
docker-compose -f stack.yml up), wait for it to initialize completely, and visit
http://host-ip:8080 (as appropriate).
ghost images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
How do you recommend we update our Ghost docker image? Use volumes and just update replace the primary container?
are there instructions or a guide anywhere to upgrade from 0.11.x to 1.0?
I have this container running ghost 0.11.10 with a data volume mounted (directory is on host not in its own container)
I tried just launching the 1.0 ghost image with the new path and it would not start
Is there a way to use my own config file with 1.7.1 ghost?
just set environment variables:
please note that
url is lowecase.
I guess you can set other configuration through env. variables, but I never tried.
Hope this helps :)
Agree with rgarrigue, definetely an 'issue' in 1.7.1 image.
Latest image got an "issue" : doc say you should put /var/lib/ghost/current/content/ on a volume, but config.production.json is located in /var/lib/ghost/ which make it non persistent. And there's the localhost:2368 there that got to be updated if you want your link going to yourdomain.com.
What about updating nginx in docker base image?
Not sure if I did something weird or if this is documented somewhere, but it looks like the content directory is actually:
which is a symlink to /var/lib/ghost/versions/1.5.0.
docker run --name blog -p 8080:2368 -v /data/blog/content:/var/lib/ghost/content ghost:latest