Missing Rails.application.secrets.openid_connect_signing_key for production environment. The secret will be generated and stored in config/secrets.yml.

[xiaoyawl]

I run the latest yml.And I get the problem

here it's logs

Setting up GitLab for firstrun. Please be patient, this could take a while...
Missing Rails.application.secrets.openid_connect_signing_key for production environment. The secret will be generated and stored in config/secrets.yml.
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::registry...
Configuring gitlab::pages...
Configuring gitlab-shell...
Configuring nginx...
Configuring nginx::gitlab...
Setting up GitLab for firstrun. Please be patient, this could take a while...
Missing Rails.application.secrets.openid_connect_signing_key for production environment. The secret will be generated and stored in config/secrets.yml.```

[Wyall]

I get the same, after that message everything tries to restart and it happens again and again. Is your's a QNAP by any chance? Mine is and I have the feeling their docker implementation is weird in many regards. Not sure if that's the problem here though.

[qq339837609]

I have the same question and can't start docker.

[HsuNick]

version is 10.8.3-1?

[Wyall]

I think I tried 10.8.2, I quickly tried 10.8.3-1 now, seemed to have worked for me. From what I saw a key was found, then a restart and then everything spawned correctly.

[jboxberger]

Same Problem with 10.8.3-1 directrly after the Update. After a Container resatart it seems to work.

[ulrichSchreiner]

same here, 10.8.3-1. looks like #1625

[KonstantinKuklin]

same on 10.8.3-1, 10.8.2

[KonstantinKuklin]

wasted 1 hour, but the problem not relevant for Missing Rails.application.secrets...
What's going on there:

• docker trying to start /sbin/entrypoin.sh
• find command to execute - /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf &
• go to hell with - kill -15 $SUPERVISOR_PID
• trying to restart

was added in f31c4d7

[dimm0]

My understanding is that supervisord is supposed to be starting 2 times - first for initial config, and second for running the services. So it's starting supervisord, then killing it and waiting for all processes to finish, and then starting again. Not sure why though..

[dimm0]

Still not fixed in the last 10.8.4 release

[Nepoxx]

I might be missing something but from reading the comments it seems like restarting the container after upgrading fixes this issue? Can anyone confirm this?

[dimm0]

Not for me. It keeps restarting with the same error

[Nepoxx]

I had this issue and therefore stayed on 10.8.1, I just updated to 11.0.1 and I no longer have this issue.