this is what the pipeline is doing

    - git config --local http.sslverify false
    - git remote add vcs https://${VCS_USER}:${VCS_PASS}@${VCS_GIT}/${CI_PROJECT_NAME}
    - git fetch origin
    - git fetch vcs
    - git submodule update --remote
    - git push vcs HEAD:refs/heads/${CI_COMMIT_BRANCH}
    - git push vcs HEAD:${CI_COMMIT_REF_NAME}
    - git push --tags

I'm trying to get a postgres service working with act runner 0.2.6. But the service container does not become available for the job container and there is no logging to indicate any problems. The service definition is the following ``` services:
postgres:
image: postgres
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5

Does anyone have suggestions to investigate this?

I'm trying to get a postgres service working with act runner 0.2.6. But the service container does not become available for the job container and there is no logging to indicate any problems. The service definition is the following:

postgres:
image: postgres
options: >-
--health-cmd pg\_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5

Does anyone have suggestions to investigate this?

I'm trying to get a postgres service working with act runner 0.2.6. But the service container does not become available for the job container and there is no logging to indicate any problems. The service definition is the following:

  postgres:
    image: postgres
    options: >-
      --health-cmd pg\_isready
      --health-interval 10s
      --health-timeout 5s
      --health-retries 5

Does anyone have suggestions to investigate this?

I'm trying to get a postgres service working with act runner 0.2.6. But the service container does not become available for the job container and there is no logging to indicate any problems. The service definition is the following:

  postgres:
    image: postgres
    options: >-
      --health-cmd pg\_isready
      --health-interval 10s
      --health-timeout 5s
      --health-retries 5

The job cannot resolve the postgres hostname and the container does not stay alive while the job is running. Does anyone have suggestions to investigate this?