-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GHA cache doesn't work when building multiple images #497
Comments
I tried separating them into 2 jobs and the short job seems to break the cache for the longer job. So the whole action can only have one image cache? My current workaround is remove caching for the shorter job. So I can have the time saving on the significantly longer job. |
This started happening to me today. last working build was able to load all build context but now it doesn't load all. failing build context load:
working build context load:
this issue started happening since commit #9ed5823618d7aa277d31c9106594ecb63692bef4 I currently cannot push my images to dockerhub. I did not even change any content of code related to build |
@quanton-dev, was you able to solve it? I have the same issue and it stopped working 7 days ago when the commit was made. @crazy-max, any ideas why load build context is smaller than before? |
I changed my I first deleted my .dockerignore and it works again and after that I configured my .dockerignore from this:
to this:
and works like normal. I had to do some research but couldnot find any kind of reason why it would change how it reads .dockerignore file. You might want to check your .dockerignore first. or is it related to this project? I don't know. @mikhailredis as I can see in your mentioned issue repository you have similar .dockerignore might be related? |
@quanton-dev, Thank you for the response. I have a very similar |
@crazy-max, any ideas how |
Yes this is a known issue with buildx 0.7.0. See docker/buildx#850 (comment) as a workaround in the meantime. |
@crazy-max, thank you. I updated the I hope it's going to be fixes in the future versions. |
@mikhailredis Yes will be fixed with buildx 0.7.1 (docker/buildx#858). |
Hello, I am using |
Is this by design and what is the recommended way of using it?If it's a bug, please confirm. Thanks!Looks like it's been confirmed as a bug.
^ This takes 28s to finish after the first run
The following takes 4 minutes every single run. And the second app is actually simpler, so it shouldn't have taken much longer.
The truth is the cache is not used at all.
The text was updated successfully, but these errors were encountered: