What changed
On August 18, 2026, Ghost’s Platform team said Ghost 6.x will be the last major release line usable with Ghost-CLI. When Ghost 7.0 ships, Ghost’s Docker Compose setup will become the official self-hosting method and Ghost-CLI will receive no further updates except urgent security fixes. Ghost says it will add missing capabilities such as multi-site support and local theme development to the Docker setup and provide a documented, supported migration path for existing CLI installs. The team also plans breaking changes to the Ghost 7 Docker image, including removing Ghost-CLI from the image, moving the content volume to /home/ghost/content, and running as a dedicated ghost user rather than node.
Why it matters
This is a deployment-contract change for self-hosted Ghost operators, agencies and small teams. The familiar CLI-based install/update model is being retired in favor of a multi-service Compose stack that includes Ghost, MySQL and Caddy and can also orchestrate analytics and ActivityPub services. Operators will need to revisit backups, upgrades, filesystem mounts, reverse-proxy assumptions, automation and server sizing. The move is also strategically important because Ghost is using containers to keep newer platform features outside the core process while still making them available to self-hosters.
Ghost-CLI has a defined end-of-line
Ghost’s Platform team says the 6.x release line is the final major version that will work with Ghost-CLI. After Ghost 7.0, the CLI is slated to stop receiving normal updates, with only urgent security fixes considered. That turns a previously gradual shift toward Docker into a concrete support boundary for operators who still depend on `ghost install`, `ghost update`, systemd and Nginx workflows managed by the CLI.
Docker Compose becomes the supported operating model
Ghost’s current Docker documentation already exposes the replacement stack in preview. It provisions Ghost with MySQL and Caddy through Docker Compose and can add analytics and ActivityPub services through Compose profiles. Updates become a repository-and-image workflow—pull configuration changes, pull container images and recreate services—rather than the CLI directly managing a host install.
Ghost is building a migration path rather than forcing a clean reinstall
The Docker tooling includes a migration assistant for existing Ghost-CLI installations. Ghost documents an in-place flow that copies content, dumps and imports the database into containerized MySQL, stops the existing Ghost and Nginx services, starts Caddy, and provides rollback instructions. The Platform team says this migration path will be documented and supported before Docker fully replaces the CLI.
The Ghost 7 image itself will introduce breaking operational changes
Ghost says the 7.0 image will remove Ghost-CLI, move the content volume from `/var/lib/ghost/content` to `/home/ghost/content`, and run as a dedicated `ghost` user instead of `node` while retaining uid/gid 1000:1000. Those changes can affect bind mounts, backup scripts, permission handling and custom Docker overrides even for operators already using containers.
The replacement stack is not yet declared complete
Ghost explicitly says work remains before the Docker setup can fully replace Ghost-CLI. Multi-site support and first-class local theme development are named gaps that must be filled, and the current installation documentation still labels Docker as a preview. The migration direction is firm, but builders should not assume every CLI workflow is already feature-complete in Compose today.