fix: allow non-0 GID process to access and execute

[ymartin59]

When running container from a docker compose using a service account (for instance UID=1000 and GID=1000), execution fails with

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/opt/sonarqube/docker/entrypoint.sh": stat /opt/sonarqube/docker/entrypoint.sh: permission denied: unknown

Exerpt of docker compose:

  sonarqube:
    image: docker.io/library/sonarqube:
    user: "1000:0"
    hostname: sonarqube
    container_name: sonarqube
    read_only: true
    depends_on:
      db:
        condition: service_healthy
      traefik:
        condition: service_started
    environment:
      SONARQUBE_UID: 1000
      SONARQUBE_GID: 1000

Not tested but I am convinced this same issue prevents execution "as is" in Kubernetes context.

Thank you in advance for your help,
Yves