shuaichang

> I thought if k8s couldn't make use of it it wouldn't be worthwhile to keep @dcantah my understanding is that K8s could make use of it by adding annotations...

@lihuiba that's correct. The end goal is to use a single OCIV1 image that can be run with/without acceleration for easier rolling updates, rollback, image security scanning etc.

Another option is that the overlaybd-ctr could be independent from overlaybd damonse (tcmu and snapshotter), also not require containerd config change: https://github.com/containerd/accelerated-container-image/blob/main/docs/IMAGE_CONVERTOR.md ``` # bin/ctr supports image conversion without requiring...

@lihuiba that’s great to know, it will be very helpful. Any guess when can we try the conversion tool?

Thanks! We do need the lastest overlaybd-tcmu and snapshotter to work with 18.04 as switching node image is not an option. Could you add separate deb for 18.04 in the...

In which version/commit the fix was merged in?

@liulanzheng @BigVan if any block of the Overlaybd blob is corrupted, will `overlaybd-zfile --verify -t -x layerfile` be able to identify the corruption?

Also @BigVan do we know how fast the the validation of `overlaybd-zfile --verify`, is it faster than CRC32?

Thanks @BigVan for the quick reply. Do we know how much time the verification would take for a 10GB (or some other layer size) to verify? Also is it possible...

@BigVan could you clarify the following scenarios? Some background context: we download Overlaybd image blob layers by chunks concurrently and put them into registry_cache. 1. If some part of a...