How Docker and OCI image layers represent filesystem changes, why deleting a file needs special whiteout entries, and what happens if you create a file called .wh.foo.
Indeed and thanks for mentioning it! I think that’s an interesting bit of the history which i am pretty sure inspired the current design of docker layers… I did find out about this during my research and I am pretty sure i mentioned it somewhere in the article, since I kept wondering “why didn’t they just use Tar PAX headers??”
What do you mean inspired, aren’t your currently included quotes imply it was forced to go this way if it wanted to use (to unpack the base layer once and use it in many different containers) the only in-kernel union FS available back then?
Indeed and thanks for mentioning it! I think that’s an interesting bit of the history which i am pretty sure inspired the current design of docker layers… I did find out about this during my research and I am pretty sure i mentioned it somewhere in the article, since I kept wondering “why didn’t they just use Tar PAX headers??”
score 1 · canonical
What do you mean inspired, aren’t your currently included quotes imply it was forced to go this way if it wanted to use (to unpack the base layer once and use it in many different containers) the only in-kernel union FS available back then?
score 1 · canonical