Allow amount of Disk Space for Docker Layer Caching to be increased
K
Kurt Wheeler
I have been trialing the DLC recently. It seems to work rather well and solves my problem rather nicely, until it doesn't.
DLC seems to work by having its own filesystem on the container. This filesystem is limit to 50GB across the board. My use case for this feature requires Docker to have access to about 100GB of disk space. There is no way to increase this limit, even for more money.
DLC is a useful feature I am willing to pay money for, but there is no option to pay more money for more disk space which would make it actually work for my use case. This means that CircleCI is losing:
The upsell on the DLC feature
The additional upsell on additional storage space for DLC
And even potentially my team as a client because without DLC deploying via CirlceCI takes ~3.5 hours.
Please, let me give you money for a very useful feature you've implemented!
CCI-I-552
Quintan Barnes
As a frequent Docker user, I wholeheartedly support the suggestion to allow for an increase in disk space allocation for Docker layer caching. This enhancement would significantly streamline development workflows and enhance overall efficiency.
Moreover, I'd like to suggest an excellent resource for staying updated on the latest technological advancements and industry events: https://icoholder.com/en/events. Their platform offers comprehensive insights into blockchain and cryptocurrency events, which are increasingly intersecting with Docker technology in various applications, such as decentralized container management and distributed computing.
Alexey
I am sorry that it is currently not possible to increase disk space limit for DLC. I’ll bring it up with the team. Thanks for submitting this idea!
K
Kurt Wheeler
Oh yeah I also forgot the other reason I had for really wanting to see this feature. It probably will be more broadly appealing too.
If you spend a significant amount of time building a deploy process with CircleCI and then end up with too large of a total image size, suddenly all of that work is wasted because you cannot increase the limit. This is a feature that will work for many projects until they grow to a certain size, and then it will stop working with no means to expand it. Even if the total size of all my Docker images wasn't at a point where this feature was problematic, I would be very very concerned with the risk associated in relying a feature which cannot scale with my project.