Upgrade from Retool 3.114.28 → 3.148.32 causes API and Code Executor containers to restart continuously

💬 Self Hosted Retool
1

Hi everyone,

we’re running a self-hosted Retool instance (version 3.114.28) using Docker and the integrated PostgreSQL database (no externa

l DB or Workflows). We’re currently trying to upgrade to version 3.148.32, but we’re running into an issue during the process.

Following the official documentation, we upgraded step by step — moving from the last patch of one major version to the last patch of the next. The upgrade from 3.114.1 → 3.114.28 worked smoothly. However, when upgrading from 3.114.28 → 3.148.32, the system appears to complete the upgrade process successfully, but afterwards, two containers continuously restart:

  • retool-onpremise-master-api-1

  • retool-onpremise-master-code-executor-1

There are no visible errors during the upgrade process itself, but these two containers fail to stay running afterward.

Question:
Has anyone experienced a similar issue or can recommend a working upgrade path from 3.114.28 to a higher version (eventually 3.148.32)?
Any insights into what might cause these containers to restart would also be greatly appreciated.

Upgrade-path
Upgrade-path2390×954 243 KB

Environment details:

  • Deployment type: Docker-based self-hosted

  • Database: Integrated PostgreSQL

  • Current working version: 3.114.28

  • Target version: 3.148.32

  • No Workflows in use

Thanks in advance for your help!

Best,
Rayk

1 Like
2

Hi Rayk,

We are experiencing the exact same problem as you describe.

Any help from the Retool team would be appreciated!

Cheers,

Dennis

1 Like
3

I have a similar issue. Any advice from the community would be appreciated.

4

Hi.

Has anyone tried any intermediate steps?

maybe 3.148.0

kind regards
1 Like
5

Hi Rayk,

Thanks for the breakdown there.

Do you have access to the container logs for the api and code_executor services? The error messages there might help identify what’s causing this issue.

Could you also share your compose.yaml file? We’ve updated our compose setup a few times, so comparing yours with the latest version (linked here) can help highlight what’s going wrong.

Thank you!

1 Like
6

The upgrade from 1.114.28 to 1.148.0 was successful. The upgrade from 1.148.0 to 1.148.32 was not successful. I have sent the log file and the YML file by email.