shell executor fails because the gitlab-runner does a su

The job fails because the gitlab-runner does a su on the user gitlab-runner although the container is already running under this user. It would be nice to have the option to set the parameters of the entrypoint via the values . So that I can remove the option --user=gitlab-runner.

bash-5.1$ ps -ef
PID   USER     TIME  COMMAND
    1 gitlab-r  0:00 /usr/bin/dumb-init -- /bin/bash /configmaps/entrypoint
    7 gitlab-r  0:00 gitlab-runner run --user=gitlab-runner --working-directory=/home/gitlab-runner

bash-5.1$ tail -3 /configmaps/entrypoint
# Start the runner
exec /entrypoint run --user=gitlab-runner \
  --working-directory=/home/gitlab-runner

Chart-Version: 0.46.0

    podSecurityContext:
      fsGroup: 65533
      runAsUser: 100 
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
        - CAP_NET_RAW
      privileged: false
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      seccompProfile:
        type: RuntimeDefault

Logs:

Preparing the "shell" executor
00:00
Using Shell executor...
Preparing environment
00:00
su: must be suid to work properly
ERROR: Job failed: prepare environment: exit status 1. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information