massimeddu-sj

Results 14 comments of massimeddu-sj

Hi @aaron-prindle , thanks for having a look at this issue. I dug a bit into the codebase, and apparently the root cause of the issue is at: https://github.com/GoogleContainerTools/kaniko/blob/63be4990ca5a60bdf06ddc4d10aa4eca0c0bc714/pkg/executor/composite_cache.go#L79 Basically...

Hi @kt-315 , sure. Please have a look at this example repo: https://github.com/massimeddu-sonicjobs/kaniko-copy-issue-test

In our case, dev containers images don't include the source code, that currently is added via a volume at run-time. Moving to watch functionality, in our case the "replace all"...

Same issue here on Kubernetes 1.29. Thanks @jocelynthode , your work around worked just fine.

Thanks @kharyam for the patch. Unfortunately it looks like that it is not working on my setup: This is the output of `lc on` command. ``` $ lc on Traceback...

Hi @kharyam , it looks like that the litra beam also have a different buffer size for the read operations. I've created a PR that solves the issue on my...

When I log in in my POD during this heavy load periods, I can see that the server itself is generating a lot of requests to generate the emailable report:...

We have a very similar issue with v0.13.1 with command: ``` buildctl --debug build --progress plain --frontend dockerfile.v0 --local context=. --local dockerfile=clients/web/ --export-cache mode=max,image-manifest=true,oci-mediatypes=true,type=registry,ref=XXXXXX.dkr.ecr.eu-west-1.amazonaws.com/YYYYY:TAG-v0.13.1,ignore-error=true,compression=estargz,rewrite-timestamp=true --import-cache type=registry,unpack=true,ref=XXXXXX.dkr.ecr.eu-west-1.amazonaws.com/YYYYY:latest-cache-v0.13.1 --import-cache type=registry,unpack=true,ref=XXXXXX.dkr.ecr.eu-west-1.amazonaws.com/YYYYY:TAG-v0.13.1 --opt build-arg:ARCH=amd64...

> I've rolled back to 0.13.0-beta1 for now. Are both of your `--import-cache` already populated? I might have missed this step trying to reproduce in an isolated env.. I see....

> Might be a regression in #4663 (v0.13.0-rc2) ? I'm testing v0.13.0-rc1 and currently I'm not seeing the issue (but previously I noticed that could happen after a while, so...