zengxs/gitlab:16.5-ee rake aborted

[ashmckenzie]

Hi,

I just noticed zengxs/gitlab:16.5-ee fails on boot after upgrading from zengxs/gitlab:16.4-ee with:

gitlab-web-1     | gitlab Reconfigured!
gitlab-web-1     | Checking for unmigrated data on legacy storage
gitlab-web-1     | Upgrade failed. Could not check for unmigrated data on legacy storage.
gitlab-web-1     |
gitlab-web-1     | rake aborted! Don't know how to build task 'gitlab:storage:legacy_attachments' (See the list of available tasks with 'rake --tasks') Did you mean? gitlab:db:truncate_legacy_tables:main /opt/gitlab/embedded/bin/bundle:25:in 'load' /opt/gitlab/embedded/bin/bundle:25:in '<main>' (See full trace by running task with --trace)
gitlab-web-1     |
gitlab-web-1     |
gitlab-web-1     | If you would like to restart the instance without performing this
gitlab-web-1     | check, add the following to your docker command:
gitlab-web-1     | -e GITLAB_SKIP_UNMIGRATED_DATA_CHECK=true

[ashmckenzie]

Setting GITLAB_SKIP_UNMIGRATED_DATA_CHECK to true does bypass this error FYI.

[Sampozzo]

The same here.

[TheArshiyan]

@zengxs It's the exact same for me, what do you think is causing the problem?

[zengxs]

I apologize for the delayed response. I only saw this issue today.

After conducting an investigation, it appears that the issue occurred because I did not synchronize the latest commit from the upstream Dockerfile. I have now fixed this problem, and the latest image should no longer encounter such issues.

Apologies once again for any inconvenience caused.

[ashmckenzie]

I can confirm this is now fixed, thanks @zengxs 👍 🙇 Keep up the amazing work! 🚀 💪