Giuseppe Scrivano

the issue is in containers/image (used by Skopeo to pull images from a registry) and it was caused by a recent change in ostree: https://github.com/containers/image/pull/461. This was already fixed on...

/cc @alexlarsson

@peterbaouoft if the info file cannot be opened then we need to skip the container, i.e. we need to catch the exception from `open(os.path.join(fullpath, "info")` and not include the container...

yes, I agree with you that `atomic uninstall` and `atomic containers delete` should not care about the info file being present (just ignore it in case it is not there)...

@peterbaouoft can you just ignore the issue when info is not found during "uninstall" and let the uninstall continue (i.e. disable/remove the systemd files + drop the checkouts)?

Fixed with: https://github.com/projectatomic/atomic/pull/1170 @baude is cutting a new release that will contain the fix

@yuqi-zhang https://github.com/projectatomic/atomic/pull/1079 should fix 4. Unfortunately the version of gzip/flate in golang1.8 produces a different output. We need to vendor the version in golang 1.6 so we can produce the...

From my understanding of https://github.com/projectatomic/skopeo/pull/242, `skopeo copy` doesn't allow us to specify what layers to download yet. That is a blocker for atomic pull --storage ostree, as we want to...

in the meanwhile, how much work would be to filter the layers in Skopeo? I guess the work to adapt in atomic to adapt it won't be much, and we...

@pschiffe you should specify args as: ``` "prestart": [ { "path": "/usr/libexec/oci/hooks.d/oci-systemd-hook", "args": [ "oci-systemd-hook", "prestart" ] }, ``` as they are passed as they are to exec. args[0] can...