Helm installation => Gitaly pod in CrashLoopBackOff

After setting up Gitlab via Helm chart, the gitaly pod doesn’t make it into state READY and is continously restarting.
The “kubectl logs gitlab-gitaly-0 -n gitlab” shows only following WARNINGS:

{"level":"warning","msg":"grpc: addrConn.createTransport failed to connect to {/home/git/ruby.0  \u003cnil\u003e 0 \u003cnil\u003e}. Err: connection error: desc = \"trans
port: Error while dialing dial unix /home/git/ruby.0: connect: no such file or directory\". Reconnecting...","pid":61,"system":"system","time":"2021-06-24T15:49:04.521Z"}
{"level":"warning","msg":"grpc: addrConn.createTransport failed to connect to {/home/git/ruby.1  \u003cnil\u003e 0 \u003cnil\u003e}. Err: connection error: desc = \"trans
port: Error while dialing dial unix /home/git/ruby.1: connect: no such file or directory\". Reconnecting...","pid":61,"system":"system","time":"2021-06-24T15:49:04.522Z"}
{"level":"warning","msg":"spawned","supervisor.args":["bundle","exec","bin/ruby-cd","/","/srv/gitaly-ruby/bin/gitaly-ruby","61","/home/git/ruby.0"],"supervisor.name":"git
aly-ruby.0","supervisor.pid":72,"time":"2021-06-24T15:49:04.526Z"}

To further debug, I modified the command for that container , just to be able to open a shell within the gitaly container . After doing so, I manually started (first) “/scripts/entrypoint.sh …” , then “/scripts/process_wrapper” to finally launch gitaly.
But it doesn’t seem to work properly, because “/scripts/healthcheck” still doesn’t return an OK state, and gitaly doesn’t listen on TCP 8075 as specified, but only in IPv6 =>

git@gitlab-gitaly-0:/$ netstat -tulpn                                                                                                                                     
Active Internet connections (only servers)                                                                                                                                
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name                                                                          
tcp6       0      0 :::8075                 :::*                    LISTEN      -                                                                                         
tcp6       0      0 :::9236                 :::*                    LISTEN      -                  

What can I do to further debug this issue…so that at the end gitaly pod is running fine ?

Many thanks !!