How to disable cache with New Builder Environment
Is
NO_CACHE=1 supposed to work with the New Builder Environment.
I try setting it as a variables but still seeing Found cached layer for all the steps of my Dockerfile in the Build Logs.5 Replies
Project ID:
34849d22-d685-4e73-8858-fbd4fe42ea6534849d22-d685-4e73-8858-fbd4fe42ea65
Context:
I am building one of my service and it throws an "ENOENT: no such file or directory, open '/app/dist/.../file.json'" when starting the service, which fails and crashes the service.
I have 2 other services that use the same build commands and they also depends on this file, and it's successfully copied there during the build step.
I am expecting that something went wrong while building this specific commit and now I'm stuck with a "corrupted" cache.
The solution for now is deploying an old commit and it starting my service successfully
its highly likely NO_CACHE was never implemented for the new builder, if you dont need private networking during build its recommended to switch back to the new legacy builder (it uses buildkit now and is much faster than it was before)
"to the new legacy builder", does it mean the new beta builder might be replaced by the updated legacy builder? I don't need the private network, so rolling back to the legacy builder now
That worked, and also, build went from ~4min in the new beta builder, to ~1min with legacy builder. I thought living on the edge was the best.
I might just use the legacy builder for all my services again. Is there any date regarding this new builder to be the default?
honestly, I was told but i forget the exact details, and I cant find the thread anymore 😦
i think it was mentioned that we will be moving to kainko when we go to metal.