Hi all, we are trying to start our docker setup in testing mode. On

docker/sdk testing

following error occurs:

Could not wait for el_online_dev_webdriver_1 anymore. Container status: "unhealthy"

docker inspect --format "{{json .State.Health }}" el_online_dev_webdriver_1

gives us following error log:

{
  "Status": "starting",
  "FailingStreak": 1,
  "Log": [
    {
      "Start": "2022-07-26T08:02:11.49009812Z",
      "End": "2022-07-26T08:02:11.561312217Z",
      "ExitCode": -1,
      "Output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"nc\": executable file not found in $PATH: unknown"
    },
    {
      "Start": "2022-07-26T08:02:16.56699482Z",
      "End": "2022-07-26T08:02:16.661646496Z",
      "ExitCode": -1,
      "Output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"nc\": executable file not found in $PATH: unknown"
    },
    {
      "Start": "2022-07-26T08:02:21.667094616Z",
      "End": "2022-07-26T08:02:21.74625572Z",
      "ExitCode": -1,
      "Output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"nc\": executable file not found in $PATH: unknown"
    },
    {
      "Start": "2022-07-26T08:02:26.754440716Z",
      "End": "2022-07-26T08:02:26.884457843Z",
      "ExitCode": -1,
      "Output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"nc\": executable file not found in $PATH: unknown"
    },
    {
      "Start": "2022-07-26T08:02:35.560950362Z",
      "End": "2022-07-26T08:02:35.640878142Z",
      "ExitCode": -1,
      "Output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"nc\": executable file not found in $PATH: unknown"
    }
  ]
}

Does anyone know how to configure the

unkown

path? We thought this path is configured via

tests/default.yml

->

SPRYKER_TEST_WEB_DRIVER_BIN

https://docs.spryker.com/docs/scos/dev/the-docker-sdk/202204.0/running-tests-with-the-docker-sdk.html#configure-codeception

I was on vacation. Is it solved?

Hi Valerii, error still exists 😔

Will check if it's reproducible for me locally.

Hey Valerii, thanks for testing! Seems to be an individual bug in our environment then. We will further investigate