Trouble running database migrations for v1.5.5 upgrade in Docker Compose
Hi team! We're having trouble running the database migrations when upgrading our self-hosted instance from v1.4.0 to v1.5.5 using a Docker Compose setup.
The Problem:
Our one-shot migrate container fails during the yarn install step, before it can execute the yarn nx database:migrate command.
What we're seeing:
The yarn install process exits with an error after a long series of peer dependency warnings (YN0060, YN0002).
Has anyone else encountered issues with the yarn install step failing in the migrate container for recent versions? Is there a recommended workaround for the peer dependency issues, or a different way we should be triggering the migrations in a Docker Compose environment?
1 Reply
hey you should not install dependencies on your production container
It's already shipped with them
Starting from 0.53 you don't have to run any commands while upgrading it's done during the bootstrap of the container and versioned in db
You can find related logs in your twenty-server container
upgradeCommand
Please feel free to share if any errors
Also you can find and review your workspace version in databaser at core.workspace.version
It should be equal to the currently installed twenty version, if not it means you failed a previous upgrade