Unable to push to repository in docker container

I imported a git repository into GitLab running in docker. I was able to clone it on the exposed port 2222. I was unable to push to the origin, however, after making a change. Here is the output I get (with example replacing the actual host name):

Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 1.84 KiB | 1.84 MiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: ENV GL_RC not set
remote: BEGIN failed--compilation aborted at hooks/update line 20.
remote: error: hook declined to update refs/heads/develop
To ssh://gitlab.example.org:2222/lms/lms.git
 ! [remote rejected]       develop -> develop (hook declined)
error: failed to push some refs to 'ssh://git@gitlab.example.org:2222/lms/lms.git'

The config file that was created has this:

[remote "origin"]
    url = ssh://git@gitlab.example.org:2222/lms/lms.git
    fetch = +refs/heads/*:refs/remotes/origin/*

I checked the authorized_keys file for gitlab and see my public key and that the file has the user and group set to ‘git’

It seems this often happens when people include “/repositories” in the path. I have not done that, but I wonder if the group name “/lms” in front of the repository name could be an issue.

Interesting. I also get the same message about GL_RC not being set when I try to create the file through the GitLab browser interface.

I found documentation showing that this variable points to the file gitolite.rc. I thought, based on other search results, that GitLab is no longer using Gitolite.

I believe I figured this out. I imported the repository from our existing Gitolite server. The update hook was pulled over with the files. I removed it since it is not needed anymore and am able to push to the server now.