-
Notifications
You must be signed in to change notification settings - Fork 130
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
Pushing kaniko-chains to kind-registry #1199
Comments
I usually do something like this: # Change this to the name of your kind cluster
export KIND_CLUSTER_NAME=kind
export KO_DOCKER_REPO='kind.local'
ko apply --sbom none -f <(
kubectl -n tekton-chains patch deployment tekton-chains-controller --type='json' \
-p '[{
"op": "replace",
"path": "/spec/template/spec/containers/0/image",
"value": "ko:/tektoncd/chains/cmd/controller"
}]' \
--dry-run=client -o yaml
)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was wondering if anyone else got the following error while running
tkn task start --param IMAGE=kind-registry:5000/kaniko-chains --use-param-defaults --workspace name=source,emptyDir="" --workspace name=dockerconfig,secret=docker-credentials kaniko-chains
"https://kind-registry:5000/v2/": http: server gave HTTP response to HTTPS client?
I've added that repo to insecure registries for my local docker engine:
Insecure Registries:
kind-registry:5000
127.0.0.0/8
The text was updated successfully, but these errors were encountered: