-
-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
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
Unable to execute tests when they are running in Jenkins with Kubernetes plugin when Pods are running in EKS #243
Comments
ikolomiyets
added a commit
to ikolomiyets/testcontainers-go
that referenced
this issue
Sep 17, 2020
… to run the tests in the Docker environment with disabled "bridge" network. The CreateContainer or CreateNetwork function will check if bridge network exists and if does not it creates a reaper_default network and ensure that container is attached to the reaper_default network.
ikolomiyets
changed the title
Unable execute tests when they are running in Jenkins with Kubernetes plugin when Pods are running in EKS
Unable to execute tests when they are running in Jenkins with Kubernetes plugin when Pods are running in EKS
Sep 17, 2020
gianarb
added a commit
that referenced
this issue
Sep 18, 2020
Issue #243: Introducing the default network in case "bridge" is disabled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The pipeline is running in Jenkins instance with Kubernetes plugin. Both Jenkins and Kube plugin pods are running in the EKS.
Tests are failing when trying to create Reaper container, i.e. it times out when waiting for the Reaper to come alive.
To Reproduce
Set up Jenkins server with a Kubernetes cloud defined which connectes to a EKS instance.
A test scenario uses Testcontainers to create a container.
A test step just run
go test
.The following error appears in the output:
Expected behavior
Test succeeds
** docker info **
Additional context
There are two issues related to the EKS and similar setup:
bridge
network disabled. This pretty much means that any port exposure has no effect but does not fail either as in this casenone
network becomes default which means no networking. Reaper has currently no option to use a non default network which leads to the failure.bridge
network does not exist, althouh I'm surprised that it did not fail in this case.I have a working code that rectifies the above error but need to do a bit more cleaning prior to submitting PR.
The text was updated successfully, but these errors were encountered: