Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Docker hub image cache doesn't seem to be working #19583
We have a continuous integration pipeline on circleci that does the following:
I ran the build twice in a row, and I see a lot of crossover in the hash of the layers being pushed. Yet rather than "Image already exists" I see "Image successfully pushed".
If you diff those two files you'll see that only 2 layers differ in each build:
So why is it that all the images have to re-push every time?
It seems they have their own fork of docker they're using in the env...
in addition, running:
also gives me
I think it's the save/load that's causing problems here. Docker caches hashes of the layers in
Ideally CircleCI would offer a way to preserve the
ah. it seems what's going on is that the cache is saved after the dependencies step, which is obviously before deployment (docker push) runs...trying to come up with a good solution here - i'll keep updating the thread for anyone else who runs into this issue but as it's obviously not a docker issue i'll close it
For anyone else who ends up here:
There is a "better" solution needed to be implemented on the CircleCI side in terms of the cached dirs and stuff. However one issue is that CircleCI is on 1.8.x. The 1.9.1 upgrade greatly improves buffering for pushes. You can enable 1.9.1, see here: https://discuss.circleci.com/t/docker-1-9-1-is-available/1009.
This improved my buffer/push speed in Circle significantly.