-
Notifications
You must be signed in to change notification settings - Fork 121
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
Dockerfile for other CI providers #47
Comments
Hi Max, I understand the need - though using a different base image also means I'd have to keep it up to date. What do you need, just a Dockerfile or also a full docker image hosted somewhere? |
just leaving a small comment here, as we're maintaining our own you can either just call kubeconform:
stage: analysis
image: kiwicom/kubeconform
cache:
key: "kubeconform-${CI_COMMIT_REF_SLUG}"
paths:
- .cache/
script:
- kubeconform -cache .cache -summary -exit-on-error k8s or use our kubeconform:
stage: analysis
image: kiwicom/kubeconform
cache:
key: "kubeconform-${CI_COMMIT_REF_SLUG}"
paths:
- .cache/
variables:
KUBECONFORM_CACHE: .cache
script:
- analyse k8s or feel free to just take as inspiration for anything else 😅 |
The Dockerfile currently doesnt seem to work on GitLab CI for example, as GL-CI expects to be able to oppen up a shell in the container and execute the cmd that way.
Just specifying entrypoint and args isnt allowed by gitlab and treatet as an invalid config.
For the dokcer image to work properly with Gitlab CI there would need to be a shell inside the container, although the entrypoint could just remain as it is right now.
The text was updated successfully, but these errors were encountered: