public_git
/
kaniko
mirror of https://github.com/GoogleContainerTools/kaniko
1
0
Fork 0
Code Issues Releases Wiki Activity

Clarify why merging into another container is a bad idea (#2965) 

I tend to read 'YMMV' as 'might need some jiggling'. I think being explicit about the particular implementation details is more useful here.
This commit is contained in:
timbavtbc 2024-01-30 22:22:27 +00:00 committed by GitHub
parent 0a7971e4d4
commit 0733ec1944
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -19,7 +19,7 @@ standard Kubernetes cluster.
kaniko is meant to be run as an image: `gcr.io/kaniko-project/executor`. We do kaniko is meant to be run as an image: `gcr.io/kaniko-project/executor`. We do
**not** recommend running the kaniko executor binary in another image, as it **not** recommend running the kaniko executor binary in another image, as it
might not work. might not work as you expect - see [Known Issues](#known-issues).
We'd love to hear from you! Join us on We'd love to hear from you! Join us on
[#kaniko Kubernetes Slack](https://kubernetes.slack.com/messages/CQDCHGX7Y/) [#kaniko Kubernetes Slack](https://kubernetes.slack.com/messages/CQDCHGX7Y/)
@ -150,9 +150,12 @@ image (if there are any) and update image metadata.
- kaniko does not support building Windows containers. - kaniko does not support building Windows containers.
- Running kaniko in any Docker image other than the official kaniko image is not - Running kaniko in any Docker image other than the official kaniko image is not
supported (ie YMMV). supported due to implementation details.
- This includes copying the kaniko executables from the official image into - This includes copying the kaniko executables from the official image into
another image. another image (e.g. a Jenkins CI agent).
- In particular, it cannot use chroot or bind-mount because its container must
not require privilege, so it unpacks directly into its own container root
and may overwrite anything already there.
- kaniko does not support the v1 Registry API - kaniko does not support the v1 Registry API
([Registry v1 API Deprecation](https://engineering.docker.com/2019/03/registry-v1-api-deprecation/)) ([Registry v1 API Deprecation](https://engineering.docker.com/2019/03/registry-v1-api-deprecation/))