gitlab runner flyctl fails to start a rails app

Hi Fly’s team,
I setup a gitlab CI/CD deploying a rails app to fly platform and it failed at the application starting step:

deployment-01GHDKQ9HH4VZHP339SEF4BJ2W: digest: sha256:b72d14d51b386ab86c90b94a2ed1c3f819c091442c1f0d80e43fac0b13c5800a size: 3265
--> Pushing image done
image: registry.fly.io/terminal-s1:deployment-01GHDKQ9HH4VZHP339SEF4BJ2W
image size: 1.1 GB
==> Creating release
--> release v9 created
--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: bin/rails fly:release
--> This release will not be available until the release command succeeds.
	 Starting instance
	 Configuring virtual machine
	 Pulling container image
	 Unpacking image
	 Preparing kernel init
	 Configuring firecracker
	 Starting virtual machine
	 Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
	 no label, UUID=817d8c70-2d2a-4600-acfc-b9816fafb4cf
	 2022/11/09 07:34:20 listening on [fdaa:0:8645:a7b:d86c:a105:919c:2]:22 (DNS: [fdaa::3]:53)
	 Starting instance
	 Configuring virtual machine
	 Pulling container image
	 Unpacking image
	 Preparing kernel init
	 Configuring firecracker
	 Starting virtual machine
	 Starting init (commit: 81d5330)...
	 Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
	 no label, UUID=817d8c70-2d2a-4600-acfc-b9816fafb4cf
	 Preparing to run: `bin/rails fly:release` as root
	 2022/11/09 07:34:20 listening on [fdaa:0:8645:a7b:d86c:a105:919c:2]:22 (DNS: [fdaa::3]:53)
	 /app/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.5.1/lib/active_support/dependencies.rb:299:in `load_dependency'
	 /app/vendor/bundle/ruby/2.7.0/gems/pg-1.3.5/lib/pg.rb:49:in `block in <module:PG>'
	 /app/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'

The thing is, with the same app (same Dockerfile, fly.toml files) I can deploy it from my local machine. And plus the strange thing is I used the image built from gitlab job registry.fly.io/terminal-s1:deployment-01GHDKQ9HH4VZHP339SEF4BJ2W , deploy it successfully from my local machine.
I’m suspecting the fly deploy command somehow behaves differently between gitlab and my local.

What I can tell is the image size from gitlab and my local’s are different, although they’re both from a remote builder

regards and thanks
quan