Munish Chouhan

Build is working in dev, but cache is not working I will dig into it to fix it

> What caching is not working ? nothing is uploaded to cache repository in local testing, cache was getting exported to registry:

> I see. Seems working similar to Kaniko not exactly same, here we have to provide tag with the registry, so there will only be one image in the cache...

found error: ``` #12 writing cache manifest sha256:52f6bf1b49ac1d9a263cd97a071312dbc8b056d4b21e57a2c8577800bf3891af 0.2s done #12 ERROR: error writing manifest blob: failed commit on ref "sha256:52f6bf1b49ac1d9a263cd97a071312dbc8b056d4b21e57a2c8577800bf3891af": unexpected status from PUT request to https://.dkr.ecr.eu-west-2.amazonaws.com/v2/wave/build/cache/manifests/cache: 400 Bad...

now everything is working, but the caching depends upon tag, and when we use the same tag for multiple builds, it overrides the previous one, so we need to figure...

@pditommaso caching is buildkit is about caching the specific image and use the same when future build of same image comes in, its not caching layers like kaniko, where it...

I have added containerId as a tag for cache to import the correct image for any future build

> Not sure to understand how tag is used here. Can you make an example? Incase of kaniko caching is done like `--cache-repo ` but in case of buildkit two...

I am testing it locally, pods and job are getting created but blobs are not getting uploaded to aws s3 bucket working on fixing that

Testing locally is not working, so I will test it in dev