Start normally with docker-compose container but gitlab is 502

I use https://github.com/sameersbn/docker-gitlab/blob/master/docker-compose.yml
Only modified

volumes:
    - xxx

ports:
    - "3080:80"

GITLAB_PORT=3080 # 10080 Access is unavailable

sameersbn/gitlab:15.7.3 Logs

Loading /etc/docker-gitlab/runtime/env-defaults
Initializing logdir...
Initializing datadir...
Generating OpenSSH host keys... RSA DSA ECDSA ED25519 
Installing configuration templates...
Configuring gitlab...
Configuring gitlab::database...........................................................2023-01-18T05:21:05.431959713Z Loading /etc/docker-gitlab/runtime/env-defaults
Initializing logdir...
Initializing datadir...
Installing configuration templates...
Configuring gitlab...
Configuring gitlab::database.
Configuring gitlab::redis
Configuring gitlab::secrets...
Configuring gitlab::sidekiq...
Configuring gitlab::gitaly...
Configuring gitlab::monitoring...
Configuring gitlab::gitlab-workhorse...
Configuring gitlab::unicorn...
Configuring gitlab::timezone...
Configuring gitlab::rack_attack...
Configuring gitlab::ci...
Configuring gitlab::artifacts...
Configuring gitlab::lfs...
Configuring gitlab::uploads...
Configuring gitlab::mattermost...
Configuring gitlab::project_features...
Configuring gitlab::oauth...
Configuring gitlab::ldap...
Configuring gitlab::cron_jobs...
Configuring gitlab::backups...
Configuring gitlab::backups::schedule...
Configuring gitlab::registry...
Configuring gitlab::pages...
Configuring gitlab::sentry...
Configuring gitlab-shell...
Configuring nginx...
Configuring nginx::gitlab...
Setting up GitLab for firstrun. Please be patient, this could take a while...
2023-01-18 10:51:11,574 CRIT Supervisor running as root (no user in config file)
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/groups.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
2023-01-18 10:51:11,575 INFO Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
2023-01-18 10:51:11,616 INFO RPC interface 'supervisor' initialized
2023-01-18 10:51:11,616 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-01-18 10:51:11,617 INFO supervisord started with pid 587
2023-01-18 10:51:12,650 INFO spawned: 'gitaly' with pid 601
2023-01-18 10:51:12,676 INFO spawned: 'gitlab-workhorse' with pid 602
2023-01-18 10:51:12,737 INFO spawned: 'unicorn' with pid 603
2023-01-18 10:51:12,987 INFO spawned: 'sidekiq' with pid 614
2023-01-18 10:51:12,991 INFO spawned: 'nginx' with pid 615
2023-01-18 10:51:13,043 INFO spawned: 'sshd' with pid 616
2023-01-18 10:51:13,050 INFO spawned: 'cron' with pid 617
2023-01-18 10:51:14,625 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-18 10:51:14,625 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Database 'gitlabhq_production' already exists
Migrating database...
Clearing cache...

Begin with the referenced docker-compose.yml and the supplied container logs, then verify how the 3080:80 port mapping and GITLAB_PORT=3080 setting interact. Reproduce the startup and 502 response with sameersbn/gitlab:15.7.3; done means the container starts normally and the mapped address serves GitLab without a 502.