[Need Help] Can't access project page after update 15.3.3 => 15.4.0

Symptom

When accessing the project page, a 500 error occurs and cannot be accessed
Cannot interact with the server through git commands (git pull, git push, etc.)
Other gitlab pages are accessible

container Log

system

synology DS920+ DSM.2-64570
Container Manager 20.10.23-1413

action i did

Download image from Container Manager sameersbn/gitlab:15.3.5
gitlab15.3.3 container stopped
Extract gitlab15.3.3 container configuration json, create a copy
Create a copy of gitlab15.3.3.json
gitlab15.3.3 - change image name in copy.json sameersbn/gitlab:15.3.3 -> sameersbn/gitlab:15.3.5
gitlab15.3.3 - upload copy.json(gitlab15.3.5) and run container

Repeat this action from 15.3.3->15.3.5->15.4.0

What I tried to solve the problem

https://gitlab.com/gitlab-org/gitlab/-/issues/366830

docker exec -it gitlab15.4.0 /bin/bash
chown -R git:git /var/opt/gitlab/gitaly/

it didn't work because there was no gitaly folder in the path.

https://stackoverflow.com/questions/26224649/gitlab-error-500-after-updating-when-viewing-projects

docker exec -it gitlab15.4.0 /bin/bash
sudo gitlab-rake db:migrate:status
sudo gitlab-rake db:migrate
sudo gitlab-ctl stop
sudo gitlab-ctl start 

gitlab-rake command not found  Command didn't work

https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/277

sudo gitlab-ctl reconfigure
gitlab-ctl: command not found  Command didn't work

gitlab command not found Command didn't work

other..

I should have backed up before updating.
Updated without fixing the error.
it's my fault

docker run --name gitlab -it --rm \
    sameersbn/gitlab:15.3.3 app:rake gitlab:backup:create

  Please configure the database connection.
  Refer http://git.io/wkYhyA for more information.
  Cannot continue without a database. Aborting...
  

please advice to solve the problem
Thanks in advance for your advice

Start by reviewing the container logs and the upgrade sequence from 15.3.3 through 15.3.5 to 15.4.0, then compare the reported Docker configuration and available container commands. Reproduce the project-page 500 error and Git operation failures if possible; done means identifying the upgrade cause and documenting a verified recovery path.