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
After prototyping caching layers for kaniko, I've been thinking it might make more sense to extract the file system layers in order rather than in reverse. When we extract cached layers onto the filesystem, we're essentially extracting the layers "forwards", so it doesn't make sense to extract the base image "backwards" anymore since we have to remove whiteout files specified in cached layers from the file system anyway.
This should also make the hardlink problem from #282 easier to solve.
Extracting the layers of the filesystem in order will make it easier to
extract cached layers and deal with hardlinks, as mentioned in GoogleContainerTools#284
This PR implements extracting in order and adds an integration tests to
test the bug hardlinks error in GoogleContainerTools#284
It also fixesGoogleContainerTools#325
Extracting the layers of the filesystem in order will make it easier to
extract cached layers and deal with hardlinks, as mentioned in GoogleContainerTools#284
This PR implements extracting in order and adds an integration tests to
test the bug hardlinks error in GoogleContainerTools#284
It also fixesGoogleContainerTools#325
After prototyping caching layers for kaniko, I've been thinking it might make more sense to extract the file system layers in order rather than in reverse. When we extract cached layers onto the filesystem, we're essentially extracting the layers "forwards", so it doesn't make sense to extract the base image "backwards" anymore since we have to remove whiteout files specified in cached layers from the file system anyway.
This should also make the hardlink problem from #282 easier to solve.
@dlorenc WDYT?
The text was updated successfully, but these errors were encountered: