Upgrade from 0.41.5 to 0.44.0 fails
I have followed the 1-click w docker compose guide to install twenty to latest version. I seem to have gotten 0.41.5
Now I want to upgrade to latest version 0.44.0
I follow the guide on:
https://twenty.com/developers/section/self-hosting/upgrade-guide
This means that I
1. dump the postgres database.
2. Stop twenty
3. Edit .env setting TAG=0.44.0 (previous value was TAG=latest
4. Start twenty using docker compose up -d
Now it fails with this:
Am I missing something? Or is some step in the instructions missing?
Am I supposed to go through each 0.41.0 -> 0.42.0 step, and so on up until latest version?
IF this is what I am supposed to do, then it mentions 'yarn'. What does this mean? Is this something I need to install on the host in addition to docker? (apt install yarnpkg?)
39 Replies
Documentation has missing information about the
yarn part as it has to be docker exec -it twenty-server-1 yarn and not the yarn alone, I'll fix that to clear misinformation on that part
Am I supposed to go through each 0.41.0 -> 0.42.0 step, and so on up until latest version?Yes, to upgrade your instance you have to upgrade it sequentially, so in your case you have to 0.41.0 > 0.42.0 and then 0.42.0 > 0.43.0 About the 0.44.0 version, I'd wait for official release as of now, only images are prepared but necessary changes in documentation are yet to be made
I see. Thanks.
Would I also have to download a new docker-compose.yml in between the versions?
Either download or simply update the docker-compose.yml with missing variables
I tried the two yarn commmands via docker. Second one fails:
yarn command:prod upgrade-0.42
means current tag doesnt have upgrade-0.42 command. Either way, do run and then go to next version and run the upgrade-0.42 and so on.
Hello @EbenezerIbiza
Am I supposed to go through each 0.41.0 -> 0.42.0 step, and so on up until latest version?Yes
IF this is what I am supposed to do, then it mentions 'yarn'. What does this mean? Is this something I need to install on the host in addition to docker? (apt install yarnpkg?)Yarn is a package manager. It should already be installed on your machine if using one-click. We use it to run upgrade/migration scripts between version Note that starting from 0.43 you won't have to precise what version you're upgrading to, only running
upgrade
Such as yarn command:prod upgrade
I have followed the 1-click w docker compose guide to install twenty to latest version. I seem to have gotten 0.41.5If pulling latest you should not be in
0.41.5 but 0.44.2I pulled the latest when I did the install.. I guess that is a while ago.
Anyway, I tried running docker compose pull
Then I brought up the app again.
Then I ran:
docker exec -it twenty-server-1 yarn command:prod upgrade-0.42
And it fails with this:
[Nest] 222 - 03/17/2025, 9:27:06 AM LOG [InstanceLoader] AuthModule dependencies initialized
error: unknown command 'upgrade-0.42'
[Nest] 222 - 03/17/2025, 9:27:06 AM ERROR [CommanderError] error: unknown command 'upgrade-0.42'
Exception Captured
undefined
[
CommanderError: error: unknown command 'upgrade-0.42'
at Command._exit (/app/node_modules/commander/lib/command.js:461:26)
at Command.error (/app/node_modules/commander/lib/command.js:1604:10)
at Command.unknownCommand (/app/node_modules/commander/lib/command.js:1795:10)
at Command._parseCommand (/app/node_modules/commander/lib/command.js:1317:14)
at Command.parseAsync (/app/node_modules/commander/lib/command.js:936:16)
at CommandRunnerService.run (/app/node_modules/nest-commander/src/command-runner.service.js:203:14)
at CommandFactory.runApplication (/app/node_modules/nest-commander/src/command.factory.js:37:22)
at bootstrap (/app/packages/twenty-server/dist/src/command/command.js:34:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
code: 'commander.unknownCommand',
exitCode: 1,
nestedError: undefined
}
]
At this point, .env still has TAG=latest
When I try to login, I get this error:
You should do upgrade minor by minor which means 0.40 -> 0.41 0.41 -> 0.42 etc
You should not do 0.42 -> latest
I think this i what I am trying to do actually. I think I currently am on 0.41.5
If you're on the latest command to upgrade to 0-42 won't exist
My .env has always said TAG=latest. But when I last looked in Settings > Genral, it said 0.41.5
I think this i what I am trying to do actually. I think I currently am on 0.41.5You should be able to double check that in your client settings or server admin
Not sure how when I cannot login
That's because it was the latest at the time you've pulled the image I guess
Makes sense. Should I change TAG=0.42.0 and do docker compose pull?
Yes totally
I would pull the 0.42 latest version
GitHub
Tags · twentyhq/twenty
Building a modern alternative to Salesforce, powered by the community. - Tags · twentyhq/twenty
v0.42.18So I should add TAG=0.42.18 ?
Yes not sure if the v-prefix
v is needed or not
CheckingI guess without v
it should be with
Or dockerhub might fallback on both anw
Hmm.. The docs mention without....
OK. Did the pull. Now I brought up the app. Now I run docker exec -it twenty-server-1 yarn command:prod upgrade-0.42, right?
Or docker exec -it twenty-server-1 yarn command:prod upgrade-0.43?
0.42 first
OK
then you'lle do the same trick
TAG=43
UPGRADE 43 etc etc
upgrade-42 step fails:
[Nest] 136 - 03/17/2025, 9:40:58 AM LOG [InstanceLoader] GraphQLModule dependencies initialized
[Nest] 136 - 03/17/2025, 9:40:58 AM LOG [InstanceLoader] BillingModule dependencies initialized
[Nest] 136 - 03/17/2025, 9:40:58 AM LOG [InstanceLoader] AuthModule dependencies initialized
error: unknown command 'upgrade-0.42'
[Nest] 136 - 03/17/2025, 9:40:58 AM ERROR [CommanderError] error: unknown command 'upgrade-0.42'
Exception Captured
undefined
[
CommanderError: error: unknown command 'upgrade-0.42'
at Command._exit (/app/node_modules/commander/lib/command.js:461:26)
at Command.error (/app/node_modules/commander/lib/command.js:1604:10)
at Command.unknownCommand (/app/node_modules/commander/lib/command.js:1795:10)
at Command._parseCommand (/app/node_modules/commander/lib/command.js:1317:14)
at Command.parseAsync (/app/node_modules/commander/lib/command.js:936:16)
at CommandRunnerService.run (/app/node_modules/nest-commander/src/command-runner.service.js:203:14)
at CommandFactory.runApplication (/app/node_modules/nest-commander/src/command.factory.js:37:22)
at bootstrap (/app/packages/twenty-server/dist/src/command/command.js:34:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
code: 'commander.unknownCommand',
exitCode: 1,
nestedError: undefined
}
]
In your server container please run
cat package.json | grep version, and share the output$ docker exec -it twenty-server-1 cat package.json | grep version
"version": "0.44.2",
I guess it pulled the latest back then.
Oh. I forgot to comment out the TAG=latest from .env
I did that now and did pull again. Now I get this:
$ docker compose pull
WARN[0000] The "STORAGE_S3_NAME" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_ENDPOINT" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_NAME" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_ENDPOINT" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_REGION" variable is not set. Defaulting to a blank string.
[+] Pulling 5/5
✔ worker Skipped - Image is already being pulled by server 0.0s
✘ db Error manifest for twentycrm/twenty:0.42.18 not found: man... 1.2s
✔ redis Pulled 1.0s
✔ change-vol-ownership Pulled 0.9s
✘ server Error manifest for twentycrm/twenty:0.42.18 not found:... 1.2s
Error response from daemon: manifest for twentycrm/twenty:0.42.18 not found: manifest unknown: manifest unknown
You need the
v -> v0.42.18
Please format your logs using
I willl soon be running out of disk space. Can I somehow remove the old 0.41.* images?
Git pull succeeded after adding the v
Through docker rm, or using DOCKER GUI
Could you please share the related docs page ? About to update it
https://twenty.com/developers/section/self-hosting/upgrade-guide
Just ran
$ docker exec -it twenty-server-1 yarn command:prod upgrade-0.42
It failed with these errors: https://paste.yt/p27862.html
(long)Where exactly :p
Are you sure you were in 0.41.5 ?
It seems like you need to upgrade to 0.41 beforehand
It said 0.41.5 in settings
What I would do in your place, is to start again from 0.41.5 and hit
0.41 upgrade and keep going until 0.44Will try. Thanks!
Still running but got these errors https://paste.yt/p27863.html
Now it completed....
Full log here: https://paste.yt/p27864.html
Is my deployment just broken? Do I need to wipe and recreate form scratch?
I do have a backup from before I even tried attempting upgrade. Because the upgrade docs instructed me to dump postgres 😅
But not sure if that is useful now or not.
If you're willing to, just do so from the latest then
Maybe it's a good idea to restore from there, and attempt incremental upgrade from 0.41
To be sure to restart the process from scratch and not with partial higher version upgrades that might corrupt your db indeed
This means you need upgrade-0.42
We've recently refactored the
upgrade command to be easier for self hosters, starting from 0.44 each workspace will have a version
If you try running an upgrade that is not minor + 1 ( 0.44 -> 0.45 ) then it will be skip + warn in order to avoid any workspace corruption
In the very same way we plan to ship a tool that will handle incremental upgrade based on the workspace version etc