Yifan Yuan
Yifan Yuan
i have added this part of configuration #108
Yes, we need to update our HTTPClient and TLS-context in photonLibOS to support SNI. Have you tried switch the back-to-source FS 'registryFsVersion'? the default is 'v2', you might change it...
It's a good suggestion. How about including overlaybd version with short-commitID in UserAgent? eg. "overlaybd/1.1.4-2c37fee"
https://github.com/alibaba/PhotonLibOS/issues/469
Did you mean that you want overlaybd send http(s) request through http proxy during the entire lazy-loading progress
> So we can use something like Kraken and reduce the harbor load. It also seems inefficient for overlaybd to fetch a signed-url from harbor for each request. So Kraken...
https://github.com/containerd/overlaybd#standalone-usage We have a description about using overlaybd standalone. I think use this config.json will create an empty read-only ext4 device: ```json { "repoBlobUrl": "", "lowers" : [ { "file"...
> Also @BigVan do we know how fast the the validation of `overlaybd-zfile --verify`, is it faster than CRC32? No, it just read the whole file and check the crc32...
1. the corrupted data will not affect the container startup. 2. overlaybd will try to evict the corrupted chunk and download this part of data from registry 3. yes. as...