Upgrade to Retool Self Host 3.52.1-stable, Code Executor struggle to start

[zelterNN]

Hi Retool Community,

I'm trying to upgrade my Retool Self Host from 3.33.32-stable to 3.52.1-stable.

I just changed the version on two Dockerfiles, and re-build the container, now my code-executor is struggling to start:

2024-06-11 12:56:15 Running code executor container in privileged mode.
2024-06-11 12:56:15 iptables: Disallowing link-local addresses
2024-06-11 12:56:18 Running code executor container in privileged mode.
2024-06-11 12:56:18 iptables: Disallowing link-local addresses
2024-06-11 12:56:21 Running code executor container in privileged mode.
2024-06-11 12:56:21 iptables: Disallowing link-local addresses
2024-06-11 12:56:24 Running code executor container in privileged mode.
2024-06-11 12:56:24 iptables: Disallowing link-local addresses
2024-06-11 12:56:26 Running code executor container in privileged mode.
2024-06-11 12:56:15 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:19 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:21 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:24 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:26 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:29 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:33 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:41 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:54 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:57:21 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:58:13 su: user retool_user does not exist or the user entry does not contain all the required fields
2024-06-11 12:56:26 iptables: Disallowing link-local addresses
2024-06-11 12:56:29 Running code executor container in privileged mode.
2024-06-11 12:56:29 iptables: Disallowing link-local addresses
2024-06-11 12:56:33 Running code executor container in privileged mode.
2024-06-11 12:56:33 iptables: Disallowing link-local addresses
2024-06-11 12:56:41 Running code executor container in privileged mode.
2024-06-11 12:56:41 iptables: Disallowing link-local addresses
2024-06-11 12:56:54 Running code executor container in privileged mode.
2024-06-11 12:56:54 iptables: Disallowing link-local addresses
2024-06-11 12:57:21 Running code executor container in privileged mode.
2024-06-11 12:57:21 iptables: Disallowing link-local addresses
2024-06-11 12:58:13 Running code executor container in privileged mode.
2024-06-11 12:58:13 iptables: Disallowing link-local addresses

It doesn't have any issue on the previous version. Can you please suggest how should I do?

[zelterNN]

I tried the method mentioned in another thread:

[Upgrade to 3.52.1-stable] Code executor failed: Failed to apply iptables rules to disallow link-local addresses

Hi team, Here's my first post on the community forum! On my self-hosted Retool stack on Kubernetes, deployed through the Helm chart version 6.2.0, I just tried to upgrade to the new 3.52.1-stable tag and I'm seeing an error in the code-executor pod which was working well before. The pod does not have privileged access but it was working fine with 3.33.24-stable. Here's the full pod log that falls into CrashLoopBackOff Running code executor container in privileged mode. iptables: Disallowing …

But I stills have user retool_user does not exist or the user entry does not contain all the required fields error.

Besides, I do want to use Python library so running in unprivileged is not ideal for me. The same setting doesn't have this issue on the previous stable release.

[zelterNN]

I tried the 3.58.0-edge just now
it doesn't have this issue as well.....so i bet there's something wrong just with the 3.52.1-stable image to cause the issue on my exec environment

[Diego_Chavez]

Hi ZelterNN,
Currently our v 3.52.1-stable has an increase in memory usage. This could be causing some of your issues. We recently patched a v3.52.2 that is a partial fix. Our team is currently working on a follow up release that should bring memory usage back to similar levels of our last stable release. If high memory usage continues to be an issue, consider scaling your Retool infrastructure. Please let us know if you have any questions.

[zelterNN]

Hi @Diego_Chavez,

I did notice a higher memory usage but even so it only takes about half of my allocated RAM. I think the issue might be somewhere in the docker image. I'm using your 3.58.0-edge now which does not have this issue.