-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
support a docker flavor meant to be used as base image for container-based CI jobs #2325
Comments
Is there a reason you need Kaniko to do anything other than build docker images? It should not be your CI tool, IMO. We used Jenkins and used side-car containers. We had any docker-related building use the kaniko container, and our Jenkins Docker Image Build agent handle anything else. These shared a PVC so that files could be accessed by both. It worked well. Is something like this possible with Gitlab-CI? |
Well, there are sidecars, and there are services, but it's all very combersome and not reliable enough to my opinion. We use Kaniko as a base image for a job, it runs the CLI, it produces the image and pushes it to a repo - that's all great. But I need the same job to report the image somewhere using curl. Really? we need a side-car for that? I'll give you more details: the job calculates the tag, and gathers build info into a json file. So I have to gather it as an artifact that is uploaded to S3, so the job with the curl can download it, just so it can post it to consul? all that because kaniko comes with plain We solved it by creating an image that extends that kaniko with busybox and adds to that |
I'll give you two more cents here. Because of this limitation, gitlab moved to recommending launching kaniko from docker-in-docker, so you can have your base image with your tools and kaniko is lunched from docker-in-docker....? really? doesn't that defeat the purpose? |
I did it differently: I prepared with |
@gabyx so you use docker-x or docker-in-docker to launch a kaniko container? |
@osher: We use kubernetes over Jenkins CI to launch kaniko to build images. To launch a kaniko container you can use |
kaniko
is used a lot as a base image for CI job-containers.For example - Gitlab-CI instructs its users to use it. However, unintuitively, it requires:
kaniko:debug
image - which feels like a hackcurl
.I propose to support an image flavor
kaniko:ci
that is dedicated to container-based CI jobs, with:kaniko:ci
bin/sh
curl
andjq
The text was updated successfully, but these errors were encountered: