-
Kaniko step resolves the image inside the pod container, while the command step relies on Kubernetes pod scheduler to resolve image (configured as container image of job pod). Seems to me that it is a problem of k8s setup. You may create a simple pod with a container using your custom image to see if it works.
-
Thanks for the response!
A test pod also makes problems, seems like a http vs https problem.
-
Well I have a really hard time setting this stuff up.
Is there somewhere an example in the documentation where (via kubernetes) kaniko builds an image which gets executed in following job? And/or something which demonstrates the use of private registries?
-
This is no longer a OneDev issue and I can not help much here. Maybe k8s forum can help on this.
-
Ok, I'll close the issue.
-
Previous Value Current Value Open
Closed
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
OneDev 10.4.0
|
| Labels |
No labels
|
Hi,
I hit a roadblock after getting on board with OneDev quite fast:
I built a couple of images with kaniko and got kaniko to push them into my registry which I deployed in the same kubernetes cluster. It is the normal registry implementation from docker without credentials or encryption configured.
Here the log from the kaniko job:
Now it is very strange that kaniko is able to pull and push from my registry while I am not able to use the image in another job:
results to:
This blocks me from switching to OneDev for a project, any hints what I did wrong? Or is this maybe a bug?