Squashfs binary format

I wrote undocker[1], which converts a docker &quot;container&quot; to a rootfs tarball. I really wish docker container format were documented as well as squashfs here. Surprising, given Docker Inc should have had enough resources to make their most important format well documented. :)<p>Anyway, undocker requires extracting the archive before using it. Squashfs wouldn&#x27;t. Perhaps I will write a docker2squash, so we can mount and run these images immediately after download.<p>[1]: <a href="https:&#x2F;&#x2F;git.sr.ht&#x2F;~motiejus&#x2F;undocker" rel="nofollow">https:&#x2F;&#x2F;git.sr.ht&#x2F;~motiejus&#x2F;undocker</a>

Also related: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32216275" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32216275</a>

Plugging this here in case it’s useful to anyone else working with squashfs: I wrote a squashfs reader&#x2F;writer in Go: <a href="https:&#x2F;&#x2F;github.com&#x2F;distr1&#x2F;distri&#x2F;tree&#x2F;master&#x2F;internal&#x2F;squashfs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;distr1&#x2F;distri&#x2F;tree&#x2F;master&#x2F;internal&#x2F;squash...</a> (part of the <a href="https:&#x2F;&#x2F;distr1.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;distr1.org&#x2F;</a> project)

So they are using u32 for their mtime, which is better than i32 because of the y2038 problem...<p>However that just means they have just another odd 70 years left after 2038, right?