Unable to copy kaniko binary

352 views
Skip to first unread message

Hazem Moharram

unread,
Jun 26, 2020, 2:57:53 PM6/26/20
to kaniko-users
Hi!

It seems we can't copy the binary over from the kaniko image into our own image. https://github.com/GoogleContainerTools/kaniko#known-issues 

Was wondering why this is the case and if we could instead build a dockerfile that's `FROM` the kaniko image.

Thanks!

Leslie Klein

unread,
Jun 26, 2020, 3:02:20 PM6/26/20
to Hazem Moharram, kaniko-users
Just run the kaniko image as is, with the documented args. Don't try to use it in another dockerfile.

--
You received this message because you are subscribed to the Google Groups "kaniko-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kaniko-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kaniko-users/dc373856-9711-4c4e-a286-1b490888b76en%40googlegroups.com.

Hazem Moharram

unread,
Jun 26, 2020, 8:58:47 PM6/26/20
to Leslie Klein, kaniko-users
My use case necessitates that I use a dockerfile with other dependencies unfortunately. If I can't copy over the binary can I atleast use the kaniko image as my base `FROM` image?

Leslie Klein

unread,
Jun 28, 2020, 4:28:01 PM6/28/20
to Hazem Moharram, kaniko-users
kaniko is a tool that reads your Dockerfile and builds your image, and can optionally push it to a repo.
kaniko should not be part of your Dockerfile.

Hazem Moharram

unread,
Jun 28, 2020, 9:46:50 PM6/28/20
to Leslie Klein, kaniko-users
I am aware but I have a use case where I want to build an image that has the kaniko binary. If I can't copy over the binary can I atleast use the kaniko image as my base `FROM` image?

Andrey Shevchenko

unread,
Aug 12, 2021, 8:01:39 AM8/12/21
to kaniko-users
Hello,

I'm also wondering about this.

Our use case - we build images with Kaniko in Gitlab pipeline and push it to our ECR. However, we want ECR URI not to be hardcoded but obtained from aws (specifically, since we manage infra through CloudFormation - we have ECR URI as output of template and usually we get it with "aws cloudformation describe-stacks").
So, basically, we have Gitlab job (as described here: https://docs.gitlab.com/ee/ci/docker/using_kaniko.html), so build is executed inside Kaniko container and we don't have aws cli here and all my attempts to build image with aws cli and kaniko failed.

Does it make sense?

понедельник, 29 июня 2020 г. в 04:46:50 UTC+3, Hazem Moharram:
Reply all
Reply to author
Forward
0 new messages