gitlab-shell | Replacement for gitolite This repo is a mirror of https://gitlabcom/gitlab-org/gitlab-shell/

Got the same issue. I found out a service was misconfigured, lookup into the chart and found out it was about session server.

Then I simply disabled the sessionServer, that should be disabled by default (cf https://gitlab.com/gitlab-org/charts/gitlab-runner/-/commit/477f145bedcb68690d723826831d9c8c4f5b2d09) and I don't need it and it did the trick.

To fix this problem I had to migrate gitlab-secrets.json from /etc/gitlab too, because this file contains the database encryption key, CI/CD variables, and variables used for two-factor authentication.
If you fail to restore this encryption key file along with the application data backup, users with two-factor authentication enabled and GitLab Runner lose access to your GitLab server.

The issue was that I was twofold:

1. I created the post-receive script inside the linux user, instead of inside the docker.
2. I was looking for the output of the post-receive script in the wrong location. I assumed that it would produce an output in the same directory as the script is located. But the post-receive script is called from the root of the .git directy, hence that is where the output is created.

Initially I tried to overcome the issue of 2 by using an absolute path, but issue 1 implied that the absolute path that I had chosen did not actually exist inside the Docker container. Therefore, no output was created, (and I was looking in the wrong place for that output on the Linux device, instead of in the Docker container).

The manual solution I found was: First get the Docker container id with: sudo docker ps -a, which returned ... ca3ba74eb832 .... Then open the docker inside the terminal with:

In general, it's hard to modify the output of a Helm chart. You can configure things the chart author has specifically allowed using Helm template syntax but not make arbitrary changes.

Typically I would expect a chart to not include an explicit namespace: at all, and to honor the helm install --namespace option (helm template has a similar option). Configuring a Service is extremely common and I would expect the chart to have settings for that.

If you're using the official GitLab cloud native Helm Chart then it has a lot of settings, including specifically for the GitLab Shell chart. In your values.yaml file you should be able to specify

Same answer than on serverfault:

There was a problem in the Apache configuration:

A useful trick I like using is to run the printenv Linux command from a pipeline job. This will print all environment variables, including GitLab built-in variables to stdout. Then you can look through these and pick the one you want.

From what I can see, the ones that might help you are the commit SHA or commit message.

• CI_COMMIT_SHA
• CI_COMMIT_SHORT_SHA = first 8 digits of CI_COMMIT_SHA

CI_COMMIT_SHA refers to the commit on the branch from which you created the tag. Once you have the commit ID, you can use the GitLab REST API (e.g. using cURL, python requests or python-gitlab) to pull the information you need. Keep in mind that a commit may belong to multiple branches, so you'll need to figure out which one you want to target.

This is almost certainly a permissions error.

Make sure that whatever file is readable: chmod a+r /opt/gitlab/embedded/service/gitlab-rails/config/database.yml (according to the comments you already did this) AND

Make sure that all the directories are executable, which for directories allows cd'ing into that directory:

As mentioned in "Running cURL on 64 bit Windows" you are running a CmdLet called Invoke-WebRequest, which has a curl alias in Powershell.
Start by removing it: