Even tho it's marked as solved in other threads, docker layer caching isn't solved.
We switched from CircleCI to Github Actions and our builds went up in time sometimes 10x.
When is this planned to be resolved?
It should also work in a way where storage is calcualted according to layers so it doesn't suddenly charges us tons.
Thanks @nadavshatz . Github currently doesn’t have a model to support docker layer caching.
Could you please let me know more about 'storage is calcualted according to layers'?
I'm aware it's not currently supported and that's why I wrote when will it be ready.
Stating the obvious is unhelpful and clutters the thread. please avoid that.
Hi @nadavshatz ,
What do you mean 'storage is calcualted according to layers'? How it works? Could you please explain more and i will confirm with Github then.
The first question is trying to get timing to a crucial feature which is proper support to docker layer caching.
Once that will be done - the cost of storage is going to be extremely large unless existing layers won't be count twice when building from a different VM.
Let me know if things are still unclear.
No, Docker layer caching wasn't addressed at all.
Some ideas I want to test later, in the meantime:
- Using private custom Github action runners on our own (AWS/GCE), with some shared volumes to store the docker data stuff...