[Bug]: latest all-in-one-image on linux/amd64 stuck with HTTP 502 Bad Gateway, mongodb (terminated by SIGILL; not expected)

[nguyenmp]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The latest community edition image for the linux/amd64 platform on DockerHub is unable to launch MongoDB, and so all API calls fail with HTTP 502 Bad Gateway.

If I target linux/arm64, things work fine.

I'm currently running on a MacBook Pro 2024

docker run -p 3000:3000 --platform=linux/amd64 lowcoderorg/lowcoder-ce
2025-06-20 04:53:33,234 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-06-20 04:53:33,235 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/01-redis.conf" during parsing
2025-06-20 04:53:33,235 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/02-mongodb.conf" during parsing
2025-06-20 04:53:33,235 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/10-api-service.conf" during parsing
2025-06-20 04:53:33,235 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/11-node-service.conf" during parsing
2025-06-20 04:53:33,235 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/20-frontend.conf" during parsing
2025-06-20 04:53:33,239 INFO RPC interface 'supervisor' initialized
2025-06-20 04:53:33,239 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-06-20 04:53:33,239 INFO supervisord started with pid 20
2025-06-20 04:53:34,252 INFO spawned: 'redis' with pid 21
2025-06-20 04:53:34,258 INFO spawned: 'mongodb' with pid 22
2025-06-20 04:53:34,262 INFO spawned: 'api-service' with pid 23
2025-06-20 04:53:34,265 INFO spawned: 'frontend' with pid 24
2025-06-20 04:53:34,269 INFO spawned: 'node-service' with pid 25
2025-06-20 04:53:34,303 INFO success: redis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-06-20 04:53:34,304 INFO exited: mongodb (terminated by SIGILL; not expected)
2025-06-20 04:53:35,864 INFO spawned: 'mongodb' with pid 140
2025-06-20 04:53:35,898 INFO exited: mongodb (terminated by SIGILL; not expected)
2025-06-20 04:53:37,902 INFO spawned: 'mongodb' with pid 175
2025-06-20 04:53:37,922 INFO exited: mongodb (terminated by SIGILL; not expected)
2025-06-20 04:53:41,397 INFO spawned: 'mongodb' with pid 183
2025-06-20 04:53:41,420 INFO exited: mongodb (terminated by SIGILL; not expected)
2025-06-20 04:53:41,777 INFO gave up: mongodb entered FATAL state, too many start retries too quickly
2025-06-20 04:53:44,494 INFO success: api-service entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2025-06-20 04:53:44,494 INFO success: frontend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2025-06-20 04:53:44,494 INFO success: node-service entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

Expected Behavior

Launching with linux/arm64 works fine:

docker run -p 3000:3000 --platform=linux/arm64 lowcoderorg/lowcoder-ce    
2025-06-20 04:52:23,926 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-06-20 04:52:23,926 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/01-redis.conf" during parsing
2025-06-20 04:52:23,926 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/02-mongodb.conf" during parsing
2025-06-20 04:52:23,926 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/10-api-service.conf" during parsing
2025-06-20 04:52:23,926 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/11-node-service.conf" during parsing
2025-06-20 04:52:23,926 INFO Included extra file "/lowcoder/etc/supervisord/conf-enabled/20-frontend.conf" during parsing
2025-06-20 04:52:23,930 INFO RPC interface 'supervisor' initialized
2025-06-20 04:52:23,930 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-06-20 04:52:23,930 INFO supervisord started with pid 20
2025-06-20 04:52:24,941 INFO spawned: 'redis' with pid 21
2025-06-20 04:52:24,953 INFO spawned: 'mongodb' with pid 22
2025-06-20 04:52:24,960 INFO spawned: 'api-service' with pid 23
2025-06-20 04:52:24,967 INFO spawned: 'frontend' with pid 24
2025-06-20 04:52:24,976 INFO spawned: 'node-service' with pid 28
2025-06-20 04:52:24,977 INFO success: redis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

Steps to reproduce

docker run -p 3000:3000 --platform=linux/amd64 lowcoderorg/lowcoder-ce

Environment

This is latest, so lowcoder-ce 2.7.2

MacBook Pro
16-inch, 2021
Apple M1 Max
MacOS Sequoia Version 15.5 (24F74)
Docker Desktop 4.42.1 (196648) (latest)

Additional Information

No response

[nguyenmp]

Seems to only affect emulation mode. Does not reproduce when I'm running on an actual linux/amd64 platform.