The dobi cache was created back when docker loaded the entire build context before building the image. Build context loading and caching is now scoped only to files used in the ADD/COPY commands, so is now much quicker. The upgrades to docker seem to have made dobi's cache obsolete. Additionally, docker images that ADD files from remote sources appear to be handled incorrectly by dobi. The remote file should be downloaded and checked for caching purposes before assuming the image is fully cached. This is handled by docker automatically.
Does it make sense for the dobi cache to remain a feature as it currently appears today?
The dobi cache was created back when docker loaded the entire build context before building the image. Build context loading and caching is now scoped only to files used in the
ADD
/COPY
commands, so is now much quicker. The upgrades to docker seem to have made dobi's cache obsolete. Additionally, docker images thatADD
files from remote sources appear to be handled incorrectly by dobi. The remote file should be downloaded and checked for caching purposes before assuming the image is fully cached. This is handled by docker automatically.Does it make sense for the dobi cache to remain a feature as it currently appears today?