Jason Hall

/lifecycle frozen

Is there any concern about this approach potentially increasing the size of manifests to an unhealthy degree? I seem to recall that being a source of concern in https://github.com/opencontainers/image-spec/pull/826, which...

Thanks, that's helpful context. I guess my question is, what guarantees the signatures will be short, since that seems to be an implicit assumption? For example, it's sometimes a feature...

> This is a challenge. This is one reason I'm supportive of `annotations`, that have an implied length, where `data` carries an implied larger payload. We will have more details...

There are currently no plans to implement this feature. This project is staffed by volunteers, effectively. If you'd like to become one of those volunteers to implement this highly-demanded feature,...

> To me, this seems somehow out-of-scope for Kaniko, and would be better suited to an dedicated registry-manipulation tool like `manifest-tool` or `skopeo`. I agree. If you're building multiple single-platform...

> Please consider adding a "Dockerfile_test_rootless" integration test containing the simplest working directive(s) that will run. Such a test might catch bugs like the one in this issue early. (Assuming...

> In the non-working case, I manually verified in a bash shell that running /kaniko/executor as root clobbers a number of files in the /usr/bin directory at runtime. (Including touch...

Kaniko shares Dockerfile parsing logic with `docker` itself. Does this work with `docker build`?

What are you trying to do? `docker load` loads image contents from a tar archive into the container runtime environment so that it can be run. Kaniko has a similar...