-
Notifications
You must be signed in to change notification settings - Fork 20
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
add option to use local test image tarball instead of building the image #494
Conversation
some teams would like to use `kiln test` from concourse. That concourse could be shared, like runway // tpe concourse instances. These, even using authentication, are getting rate limited against dockerhub. Effectively to run kiln test, we'd first need to preload the images required to build the test image ( every FROM arg used in the Dockerfile) avoid the pull ibeing executed implicitly when docker build is run by `kiln test` To avoid having to actually build an image ( which would either require to preload the images for the Dockerfile or being able to pull from dockerhub) we could use this flag to run `docker load -i $IMAGE_PATH` instead of building. this way, the test image can be `acquired` via docker proxy registries..
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
12753b5
to
e7461cc
Compare
why?: because some CI systems cannot get past the dockerhub rate limitation. We want to use kiln test for the csb tiles. But we use the tpe / runway concourse. These instances make it impossible to communicate with dockerhub because of rate limits ( even with authenticated pulls ) We can make the `kiln test` execution work by pre loading the images that are used as FROM stages in `internal/test/Dockerfile` into the docker host we start in the concourse task. Essentially we end up pulling the images from an accessible repository, then we retag them to match the expected FROM args and that makes the implicit image build work. Instead it would be nice to avoid having to run the build stage and make kiln test consume a provided image instead so it can be run offline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@notrepo05 if the tests run well on your machine, I'm happy to approve these changes once the small changes I suggested are either incorporated or rejected by @nouseforaname.
- replace `"` with `\`` quoted strings - use closer helper function and move defer up
@crhntr I added a commit with the requested changes. |
I haven't had the bandwidth to debug the pipeline, but the integration and unit tests for It appears the tests are failing due to CI misconfiguration: Run actions/checkout@v4
with:
fetch-depth: 0
repository: pivotal-cf/kiln
ssh-strict: true
ssh-user: git
persist-credentials: true
clean: true
sparse-checkout-cone-mode: true
fetch-tags: false
show-progress: true
lfs: false
submodules: false
set-safe-directory: true
Error: Input required and not supplied: token |
recreated in #495 |
Long story short, we'd like to run
kiln test
in a shared concourse.We are prevented from doing so because we cannot pull the images that https://github.com/pivotal-cf/kiln/blob/main/internal/test/Dockerfile requires for the FROM steps.
We are using authenticated pulls but we still get rate limited.
We'd like to be able to prebuild the required image via the
build-oci
task and then be able to consume the prebuild image in outkiln test
task