-
Notifications
You must be signed in to change notification settings - Fork 536
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
BuildKite CI: Deployed buildkite agents can run jobs inside docker containers #4803
Comments
Thinking I get the direction we're heading here: [buildkite jobs] IN [docker containers] executed by [buildkite agents] as [kubernetes pods] running on GKE: but yea, just some thoughts on the job execution technique:
^^^ only a single opinion here in addition to comments in the linked issue but I'd have to agree with the DinD approach (tl;dr - dind-safe image and sidecar w/ pod-host daemon graph storage mounted), mostly due to simplicity (single container add in buildkite agent pod) but its security and reliability guarantees in a kubernetes context don't hurt either 🛠️ |
Not sure if we could generate an extra pod container within a helm chart deployment, etc. rendering using the |
@bkase @yourbuddyconner, just an update:
|
Preferably via Docker-out-of-docker (bind-mounting the docker daemon socket) on GKE. As a proof-of-concept, stick a tiny job in a pipeline that runs itself in a different docker container.Note: There is a discussion on the official buildkite helm charts repo about a quirk of getting this to work on GKE buildkite/charts#54 -- giving a little buffer on time here just case this turns out to be especially annoying.
If necessary this is when we could bake our own buildkite agent image.
Depends on #4802
Epic: #4762
The text was updated successfully, but these errors were encountered: