qi0523
qi0523
> I have the same error, but adding `apiHostProto: "https"` didn't work > > ``` > [lyuze@storage-2 openwhisk-deploy-kube]$ kubectl get pods -n openwhisk --watch > NAME READY STATUS RESTARTS AGE...
/etc/overlaybd/overlaybd.json: ``` { "logConfig": { "logLevel": 1, "logPath": "/var/log/overlaybd.log" }, "cacheConfig": { "cacheType": "file", "cacheDir": "/opt/overlaybd/registry_cache", "cacheSizeGB": 4 }, "gzipCacheConfig": { "enable": true, "cacheDir": "/opt/overlaybd/gzip_cache", "cacheSizeGB": 4 }, "credentialConfig": {...
> @dbfancier if p2p is used, cache is managed by p2p, so nothing could see in /opt/overlaybd/registry_cache. You can refer to this [config file](https://github.com/data-accelerator/dadi-p2proxy/blob/main/dadip2p.yaml) to configure p2p. And @Coldwings is...
I want to implement P2P lazy pulling with containerd and stargz-snapshotter. Each node deploys a `agent` listening to 5001, which implements p2p distribution. When i use `ctr-remote image rpull docker.io/qi0523/ubuntu:latest`...
> @qi0523 Could you provide a reproducible step and the log for that issue? There are several docs for IPFS + stargz-snapshotter. Have you followed some of these steps? >...
> @qi0523 So you're implementing your own registry API, right? Does that API fully implements OCI Distribution Spec? For successful lazy pulling, it needs to implement HTTP Range Request for...
Oct 25 08:13:54 xv6 containerd-stargz-grpc[645]: {"key":"default/6/extract-643806365-5X68 sha256:73d944bd82a9c645ec64e7a4b41e2453945687efcfd83b8c268150107fab2058","level":"info","msg":"preparing filesy stem mount at mountpoint=/var/lib/containerd-stargz-grpc/snapshotter/snapshots/4/fs","parent":"","time":"2022-10-25T08:13:54.693558513Z"} Oct 25 08:13:54 xv6 containerd-stargz-grpc[645]: {"key":"default/6/extract-643806365-5X68 sha256:73d944bd82a9c645ec64e7a4b41e2453945687efcfd83b8c268150107fab2058","level":"debug","mountpoint":"/var/lib /containerd-stargz-grpc/snapshotter/snapshots/4/fs","msg":"resolving","parent":"","src":"192.168.56.106:5001/qi0523/ubuntu:latest/sha256:407f4ecfeabd9e7fefbbeb23d447c74ff234d01da7b6d88c3a3afb27c60939c6 ","time":"2022-10-25T08:13:54.703000767Z"} Oct 25 08:13:54 xv6 containerd-stargz-grpc[645]: {"digest":"sha256:407f4ecfeabd9e7fefbbeb23d447c74ff234d01da7b6d88c3a3afb27c60939c6","error":null,"key":"default/6/extract-643806365-5X68 sha256:73d944bd 82a9c645ec64e7a4b41e2453945687efcfd83b8c268150107fab2058","level":"debug","mountpoint":"/var/lib/containerd-stargz-grpc/snapshotter/snapshots/4/fs","msg":"using default...
> @qi0523 > > > http: server gave HTTP response to HTTPS client > > The error message says the `server gave HTTP response to HTTPS client`. So could you...
> @qi0523 > > > Another question is that when we use stargz-snaphotter, layer.tar doesn't exist in directory /var/lib/containerd/io.containerd.content.v1.content/blobs/sha256. > > This is because of lazy pulling. containerd doesn't pull...