What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi all, we are trying to start our docker setup in testing mode. On `docker/sdk testing` following e
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
Comments
-
Maybe @ULYHPR789 @valerii.trots?
0 -
I was on vacation. Is it solved?
0 -
Hi Valerii, error still exists π
0 -
Will check if it's reproducible for me locally.
0 -
Could you please provide more details\steps to reproduce maybe?
Couldn't reproduce the problem using our demo shops.0 -
Hey Valerii, thanks for testing! Seems to be an individual bug in our environment then. We will further investigate
0 -
Update: we've notice our webdriver docker image with latest tag was not up to date.
docker pull spryker/chromedriver
resolved it!0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random