We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes we have a test step where they need to run inside a docker image (dind), because a few tests are written with the TestContainer library.
To achieve it, we need to configure one step like this:
allTests: image: docker:24.0.9 commands: - apk add openjdk17 - dockerd-entrypoint.sh --registry-mirror=http://myprivate-mirror.ior:5000 1> /dev/null 2> /dev/null & - ./gradlew test myTEST when: event: push
This example is in the easy mode, but sometimes we need to install more than one jdk or the dind image doesn't have the library in the OS packages.
The solution was to add into the backend_options a way to create a side container with the main step container.
backend_options
allTests: image: openjdk17 commands: - ./gradlew test myTEST when: event: push backend_options: kubernetes: container: - image: docker:dind env: []
Then both containers can start and we can access the docker in the local host and execute the tests with the TestContainers.
No response
next
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Clear and concise description of the problem
Sometimes we have a test step where they need to run inside a docker image (dind), because a few tests are written with the TestContainer library.
To achieve it, we need to configure one step like this:
This example is in the easy mode, but sometimes we need to install more than one jdk or the dind image doesn't have the library in the OS packages.
Suggested solution
The solution was to add into the
backend_options
a way to create a side container with the main step container.Then both containers can start and we can access the docker in the local host and execute the tests with the TestContainers.
Alternative
No response
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: