motiejus/undocker
1
Fork 0
Code Packages Releases Activity

update doc formatting

Browse Source
This commit is contained in:
Motiejus Jakštys 2021-05-31 21:44:17 +03:00
parent 12d13c5c98
commit ccdea382b6
1 changed files with 26 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
rootfs/doc.go
View File

@ -5,30 +5,31 @@
// It will also reasonably process those files. // It will also reasonably process those files.
// //
// == Non-directory will be copied only once == // == Non-directory will be copied only once ==
//
// A non-directory will be copied only once, only from within it's past // A non-directory will be copied only once, only from within it's past
// occurrence. I.e. if file /a/b was found in layers 0 and 2, only the file // occurrence. I.e. if file /a/b was found in layers 0 and 2, only the file
// from layer 2 will be used. // from layer 2 will be used.
// Directories will always be copied, even if there are duplicates. This is // Directories will always be copied, even if there are duplicates. This is
// to avoid a situation like this: // to avoid a situation like this:
// layer0: // layer0:
// - ./dir/ // ./dir/
// - ./dir/file // ./dir/file
// layer1: // layer1:
// - ./dir/ // ./dir/
// - ./dir/file // ./dir/file
// In theory, the directory from layer 1 takes precedence, so a tarball like // In theory, the directory from layer 1 takes precedence, so a tarball like
// this could be created: // this could be created:
// - ./dir/ (from layer1) // ./dir/ (from layer1)
// - ./dir/file1 (from layer1) // ./dir/file1 (from layer1)
// However, imagine the following: // However, imagine the following:
// layer0: // layer0:
// - ./dir/ // ./dir/
// - ./dir/file1 // ./dir/file1
// layer1: // layer1:
// - ./dir/ // ./dir/
// Then the resulting tarball would have: // Then the resulting tarball would have:
// - ./dir/file1 (from layer1) // ./dir/file1 (from layer1)
// - ./dir/ (from layer0) // ./dir/ (from layer0)
// Which would mean `untar` would try to untar a file to a directory which // Which would mean `untar` would try to untar a file to a directory which
// was not yet created. Therefore directories will be copied to the resulting // was not yet created. Therefore directories will be copied to the resulting
// tar in the order they appear in the layers. // tar in the order they appear in the layers.
@ -53,12 +54,13 @@
// top dir>/.wh..wh.aufs`. // top dir>/.wh..wh.aufs`.
// //
// My interpretation: // My interpretation:
// - a file/hardlink called `.wh..wh..opq` means that directory contents from //
// 1. a file/hardlink called `.wh..wh..opq` means that directory contents from
// the layers below the mentioned file should be ignored. Higher layers may add // the layers below the mentioned file should be ignored. Higher layers may add
// files on top. // files on top. Ambiguity: should the directory from the lower layers be
// * Ambiguity: should the directory from the lower layers be removed? I am // removed? I am assuming yes, but this assumptions is baseless.
// assuming yes, but this assumptions is baseless. //
// - if file/hardlink `.wh.([^/]+)` is found, $1 should be deleted from the // 2. if file/hardlink `.wh.([^/]+)` is found, $1 should be deleted from the
// current and lower layers. // current and lower layers.
// //
// Note: these may be regular files in practice. So this implementation will // Note: these may be regular files in practice. So this implementation will
@ -71,5 +73,6 @@
// problems reading it[2]. // problems reading it[2].
// //
// [1]: https://manpages.debian.org/unstable/aufs-tools/mount.aufs.8.en.html // [1]: https://manpages.debian.org/unstable/aufs-tools/mount.aufs.8.en.html
//
// [2]: https://mgorny.pl/articles/portability-of-tar-features.html // [2]: https://mgorny.pl/articles/portability-of-tar-features.html
package rootfs package rootfs