Aleksa Sarai
Aleksa Sarai
Currently we only support single-`FROM` builds. But in Docker `17.05` (docker/docker#31257), multi-stage builds are a thing and for compatibility we need to implement it too -- shouldn't be too hard...
The previous config generation produced a config which would cause runC to run the container using the host filesystem (with no namespaces set up). While we should try to be...
If you call `image.CreateRuntimeBundleLayout` twice on the same image with the same ref, all of the files will have different `mtime`s (and `ctime`s I also believe). You can check this...
While ./cmd/... works in the canonical Go setup, I have a very interesting Go setup involving symlinks within my GOPATH. It turns out that Go doesn't like this very much...
Currently if you take a random Docker image's config file (then translate it to an OCI one using `skopeo`) you'll get a `config.json` which looks like this: ``` { "ociVersion":...
I've been playing around with skopeo+image-tools+#5+#8 and I've found that almost all of the necessary tooling we need is available. You can pull base images, create layers, validate layers, unpack...
Both `oci-unpack` and `oci-create-runtime-bundle` cannot unpack `gzip`'d layers. I haven't read what the spec says about compressed layers (and I know @vbatts has some strong opinions about it) but this...
Currently all of our tooling only really has documentation for each piece. However, once #5 and #8 are merged we will (in principle) have all of the tooling necessary to...
If you try to encrypt some data with `gpgme::encrypt` I always seem to get the following error: ``` thread 'main' panicked at 'encrypt: Error { source: Some("GPGME"), code: 32779, description:...
This came up in #48 because implementing generic comparisons means we have to come to terms with the limitations of certain spec generators. In particular, because most tar archives don't...