Akihiro Suda

Clarify that "Image Layout" is OPTIONAL

6

The current image spec explicitly says that "This layout MAY be used in a variety of different transport mechanisms" ([`image-layout.md`](https://github.com/opencontainers/image-spec/blob/710038243d857231f17df1c3f4c10850154bd1f7/image-layout.md)). However, it doesn't explicitly say that "This layout is OPTIONAL"...

CI is not triggered for pull requests

1

https://github.com/genuinetools/img/blob/54d0ca981c1260546d43961a538550eef55c87cf/.github/workflows/make-all.yml#L1 We should enable CI for pull requests as well

Slower than BuildKit with complex Dockerfile

6

Benchmark: ``` $ git clone https://github.com/moby/moby.git ./moby $ docker volume create buildbench-img $ docker run --privileged -v $(pwd)/moby:/workspace -w /workspace --rm -v buildbench-img:/home/user r.j3ss.co/img:latest build -backend overlayfs -t foo ....

Running multiple `img build` instances concurrently?

10

Running multiple `img build` instances concurrently with a single state dir is currently impossible, due to the boltdb lock. Some solutions I can come up with: * Eliminate boltdb *...

Change --no-console to --progress=(auto|plain|tty)

1

`docker build --no-console` was renamed to `docker build --progress=(auto|plain|tty)` in Docker 18.09 GA. It would be better to rename `img build --no-console` as well.

When the registry secret does not exist, job pods stucks at `PodInitializing` without human-readable error. It would be better to validate the secret name on CBI controller.

https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#handling-pod-and-container-failures

Define and implement "Flex" context provider

2

maybe like ```yaml apiVersion: cbi.containerbuilding.github.io/v1alpha1 kind: FlexContextProvider metadata: name: foo labels: mediaType: application/tar+gzip spec: template: spec: containers: - name: foo commands: ["cat", "a.tgz"] --- apiVersion: cbi.containerbuilding.github.io/v1alpha1 kind: BuildJob spec: context:...

Challenge: how to set (kind of) `batch/v1.Job` annotations from the job itself?