Official Repository

Last pushed: 7 days ago
Short Description
Ghost is a free and open source blogging platform written in JavaScript
Full Description

Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/ghost). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/ghost/tag-details.md file in the docker-library/repo-info GitHub repo.

Ghost

Ghost is a free and open source blogging platform written in JavaScript and distributed under the MIT License, designed to simplify the process of online publishing for individual bloggers as well as online publications.

wikipedia.org/wiki/Ghost_(blogging_platform)

How to use this image

$ docker run --name some-ghost -d ghost

This will start a Ghost instance listening on the default Ghost port of 2368.

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 --name some-ghost -p 8080:2368 -d ghost

Then, access it via http://localhost:8080 or http://host-ip:8080 in a browser.

You can also point the image to your existing content on your host:

$ docker run --name some-ghost -v /path/to/ghost/blog:/var/lib/ghost ghost

Alternatively you can use a data container that has a volume that points to /var/lib/ghost and then reference it:

$ docker run --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
v4.4.7

Supported Docker versions

This image is officially supported on Docker version 1.13.0.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Documentation

Documentation for this image is stored in the ghost/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

Docker Pull Command

Comments (27)
grovejc
6 months ago

Could we get a 0.9 tag please? Dockerfile seems updated to 0.9

holms
6 months ago

Why tag "latest" doesn't point to version 0.9.0 but to 0.8.0??

cyrusstoller
6 months ago

Thanks so much for the awesome work. ETA on an image for v0.9.0?

v1k0d3n
9 months ago

Have you guys thought about incorporating Let'sEncrypt for Node.js into this Docker build? I saw a thread started on the Let'sEncrypt forum, and there was this repo that looks pretty interesting: https://github.com/DylanPiercey/auto-sni

Sure, we can bake this in ourselves...but it sure would be nice to have something native from the Official Ghost Docker resource. Any thoughts?

kuceram
a year ago

Running the latest docker image, I cannot connect to it on localhost:2368. I receive no errors. Am I missing something?

webnicer
a year ago

Hey guys, I am trying to understand why you want to restart npm inside the container rather than restart the whole container?

kaithoz
a year ago

any feedback on how to restart npm within the container?

Thats somethin im also asking myself for the last 24 hours :-)

calaesha
a year ago

any feedback on how to restart npm within the container?

pinnokio
a year ago

to pmjhonwang
I spotted problem like yours (the only difference is that I'm using directories mapping to the host fs)
To solve it I duplicated following peace of code from development section into production one in config.js

// #### Paths
// Specify where your content directory lives
paths: {
contentPath: path.join(process.env.GHOST_CONTENT, '/')
}

Now it's working for me.

aholbreich
a year ago

Tag 0.7.3 is not builded