Hi, i'm currently trying the _EXPERIMENTAL_DAGGER_CACHE_CONFIG using s3 and registry. From the logs, it seems to be working
11: importing cache manifest from s3:17471463523230677791
11: importing cache manifest from s3:17471463523230677791
...
...
...
25: exporting cache to Amazon S3
25: preparing build cache for export
25: writing layer sha256:ab9a9dd810c0dc1bf1f6b911095d8f85f3b7e8d22e633e060e6f980b59ad3d23
25: writing layer sha256:ab9a9dd810c0dc1bf1f6b911095d8f85f3b7e8d22e633e060e6f980b59ad3d23 [0.01s]
25: writing layer sha256:c2ddf4c33d7561bc63d9b4cd20b5645a4528c37599dacbf0ed6b8e4df1fda6bf
25: writing layer sha256:c2ddf4c33d7561bc63d9b4cd20b5645a4528c37599dacbf0ed6b8e4df1fda6bf [0.01s]
25: writing layer sha256:c798134b5a2faa32b79b83ed0bf6b50a0117ee247c05afcb9f44ff6fd977b17c
25: writing layer sha256:c798134b5a2faa32b79b83ed0bf6b50a0117ee247c05afcb9f44ff6fd977b17c [0.02s]
25: preparing build cache for export [0.27s]
25: exporting cache to Amazon S3 DONE
but if i re-run the pipeline after deleting the volume of dagger engine, it runs like it has no cache at all. Did i miss something? i see something similar in https://github.com/moby/buildkit/issues/2274, does it relates?