Self-Hosted Build Isolation? #2330
Unanswered
ScottPierce
asked this question in
Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I currently am running Self-Hosted Runners. We have a pretty big build machine, and so I'm running Debian Linux, and have 10 runners configured directly on the machine. We were experiencing isolation issues between each of the runs, so we are using the
container
syntax and ensuring each build is run inside of a docker container.This has worked well, until we wanted to startup all of our servers and databases in CI to run tests, and we use Docker for local representations of Databases. This means that we end up running docker-in-docker, which we have found issues talking to our databases from within a container, when using docker in docker.
I have very little Kubernetes knowledge. I don't know how kubernetes creates isolation for builds. Does this project offer us a solution to our issues if we continue to use self-hosted runners? If not, does it offer a solution if we move to use google cloud as a host?
Beta Was this translation helpful? Give feedback.
All reactions