MigrationsAreLocked error on startup


#1

I’m seeing this problem when creating a fresh azure app service app, loading a ghost container. If I don’t try to map the content folders to the azure ‘home’ folder, all starts OK but I lose my data every time the app service shuffles things around internally.

If I attempt to map the ‘home’ folder to the content directory, I get this MigrationsAreLockedError

This is my docker compose file

version: '3.2'

services:

  ghost:
    image: ghost:2.2.4-alpine
    restart: always
    ports:
      - 80:2368
    volumes: 
      - ${WEBAPP_STORAGE_HOME}:/var/lib/ghost/content

Any idea why this volume mapping should cause the migration error on a brand new installation? Something to do with it trying to set up the default site and failing?


#2

I’ve tried just mapping the /var/lib/ghost/content/images (so at least I don’t lose all my images) but that just fails to run.

I asked in the ghost docker github issues, but they suggested asking here - but it seems that nobody here has any experience with the whole MigrationsAreLocked error?


#3

Ah well, nobody ever did reply here. I’ve ditched ghost containers as unusable on Azure at the moment, and moved to a standard install on a VM which turns out to be orders of magnitude simpler, faster and cheaper to run. So much for the promise of docker.


closed #4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.