kaniko
kaniko copied to clipboard
Build Container Images In Kubernetes
I am building one large docker image and I am experiencing a somewhat weird behavior that I would like to address. Host info: - Docker version: 20.10.12 - kaniko version...
**Actual behavior** Multi stage ARGs with Buildkit are evaluated and carried over stages but not in kaniko. **Expected behavior** In order to move from our Buildkit scripts to kaniko, I...
**Actual behavior** When pushing to an insecure registry, process fails with the message: ``` error checking push permissions -- make sure you entered the correct tag name, and that you...
**Actual behavior** When building multiple images (using `--cleanup` on each of them), the first build succeeds but subsequent builds fail with the following error: ``` ERROR: Process exited immediately after...
**Actual behavior** I want to transfer all files and dirs recursively from current host dir to WORKDIR inside the image I am using `COPY --chown=1001:0 . . ` **Expected behavior**...
**Actual behavior** It seems that the cache key generation is based on the the name of the base image and not on its content. That is problematic when using build-variables...
**Actual behavior** Kaniko is ignoring /etc/hosts configured by docker **Expected behavior** Kaniko should respect /etc/hosts **To Reproduce** Steps to reproduce the behavior: 1. run kaniko docker image with extrahosts for...
**Actual behavior** Using `RUN [ "chmod", "a+x", "/some/file" ]` the specified file gets the executable bit for the rest of the Kaniko run, but not in the final image **Expected...
**Actual behavior** Running kaniko in my local docker daemon, files copied with `COPY` still have my UID in the built container. This breaks reproducibility when different users build the same...
**Actual behavior** When `COPY`-ing the contents of a whole directory, Kaniko will apply metadata of that parent directory to the destination directory. This (at least) includes owner, group, and permissions....