chore(revert): revert docker info changes and rely on act_runner built-in init-stage (#48)

This PR aims to revert the change were we introduce the `docker info` command as the checker for Docker readiness.
We now rely on the act_runner's ability to do this itself.

Co-authored-by: Daan Selen <dselen@systemec.nl>
Reviewed-on: https://gitea.com/gitea/helm-actions/pulls/48
Reviewed-by: ChristopherHX <christopherhx@noreply.gitea.com>
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: DaanSelen <dselen@nerthus.nl>
Co-committed-by: DaanSelen <dselen@nerthus.nl>

templates/statefulset.yaml

@@ -48,20 +48,6 @@ spec:
           image: "{{ .Values.statefulset.actRunner.repository }}:{{ .Values.statefulset.actRunner.tag }}"
           imagePullPolicy: {{ .Values.statefulset.actRunner.pullPolicy }}
           workingDir: /data
-          command:
-          # The following is a workaround for: https://gitea.com/gitea/act_runner/issues/731
-          # We must add the docker-cli package for the server AND client cert verification.
-            - sh
-            - -c
-            - |
-              apk add --no-cache docker-cli
-              echo "Waiting for Docker daemon..."
-              until timeout 10 docker info > /dev/null; do
-                echo "Failed, retrying..."
-                sleep 2
-              done
-              echo "Docker is ready, starting act-runner..."
-              exec run.sh
           env:
             - name: DOCKER_HOST
               value: tcp://127.0.0.1:2376