Invalid mobiledoc structure error on boot 5.24.2

I just did a clean local install on ghost 5.24.2. It installed fine but I get this error on start:

Debug Information:
    OS: Raspbian GNU/Linux, v11
    Node Version: v14.17.6
    Ghost Version: 5.24.2
    Ghost-CLI Version: 1.23.1
    Environment: development
    Command: 'ghost install local'

Message: Ghost was able to start, but errored during boot with: Invalid mobiledoc structure.
Stack: Error: Ghost was able to start, but errored during boot with: Invalid mobiledoc structure.
    at ChildProcess.<anonymous> (/home/pi/.nvm/versions/node/v14.17.6/lib/node_modules/ghost-cli/lib/utils/local-process.js:75:35)
    at ChildProcess.emit (events.js:400:28)
    at emit (internal/child_process.js:910:12)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
---

Issue Summary
The server should have started without issue since it is a clean install.

Steps to Reproduce

  1. Run ghost install local or ghost start (after a new install)

Setup information

Ghost Version
5.24.2

Node.js Version
v14.17.6

How did you install Ghost?
ghost install local

Provide details of your host & operating system
Raspbian GNU/Linux, v11

Database type
local

Relevant log / error output

Debug Information:
    OS: Raspbian GNU/Linux, v11
    Node Version: v14.17.6
    Ghost Version: 5.24.2
    Ghost-CLI Version: 1.23.1
    Environment: development
    Command: 'ghost install local'
Message: Ghost was able to start, but errored during boot with: Invalid mobiledoc structure.
Stack: Error: Ghost was able to start, but errored during boot with: Invalid mobiledoc structure.
    at ChildProcess.<anonymous> (/home/pi/.nvm/versions/node/v14.17.6/lib/node_modules/ghost-cli/lib/utils/local-process.js:75:35)
    at ChildProcess.emit (events.js:400:28)
    at emit (internal/child_process.js:910:12)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)

I’ve just pushed a fix to Ghost-CLI that won’t fix this, but should hopefully output the error message properly so we might have a chance to figure out what’s wrong!