You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My goal here is to cache .esy separately from normal Docker layering but still be able to have a universal workflow where Docker works as customary both on CI and locally. I looked at --mount=type=cache - it is built for tools like esy or cargo. I posted some of my findings here:
But it still doesn't tell us how to properly save the state and later restore it.
In the current exploration, we export the whole /var/lib/docker which has large constant factors and probably requires careful pruning but I'm not familiar with how it all works.
Alternatively, there's buildx which is properly supported and probably allows us to achieve the caching we want without resorting to any hacks but alas I'm not familiar with it either.
The text was updated successfully, but these errors were encountered:
My goal here is to cache
.esy
separately from normal Docker layering but still be able to have a universal workflow where Docker works as customary both on CI and locally. I looked at--mount=type=cache
- it is built for tools like esy or cargo. I posted some of my findings here:actions/cache#260 (comment)
My biggest concerns are:
docker system prune
)I figured out how to prune everything except for the
mount cache
withdocker builder prune
:But it still doesn't tell us how to properly save the state and later restore it.
In the current exploration, we export the whole
/var/lib/docker
which has large constant factors and probably requires careful pruning but I'm not familiar with how it all works.Alternatively, there's buildx which is properly supported and probably allows us to achieve the caching we want without resorting to any hacks but alas I'm not familiar with it either.
The text was updated successfully, but these errors were encountered: