8c6ba35038
This pulls in and uses github.com/docker/docker/pkg/chrootarchive for the actual copy up which is some battle hardened code to unpack avoiding things like symlink traversal security issues. However it does pull in a pretty huge pile of vendoring, including github.com/docker/docker/pkg/reexec which we must then call at startup. It's not immediately clear that this tradeoff is the correct one. Signed-off-by: Ian Campbell <ijc@docker.com>
24 lines
1.1 KiB
Go
24 lines
1.1 KiB
Go
package archive
|
|
|
|
// Whiteouts are files with a special meaning for the layered filesystem.
|
|
// Docker uses AUFS whiteout files inside exported archives. In other
|
|
// filesystems these files are generated/handled on tar creation/extraction.
|
|
|
|
// WhiteoutPrefix prefix means file is a whiteout. If this is followed by a
|
|
// filename this means that file has been removed from the base layer.
|
|
const WhiteoutPrefix = ".wh."
|
|
|
|
// WhiteoutMetaPrefix prefix means whiteout has a special meaning and is not
|
|
// for removing an actual file. Normally these files are excluded from exported
|
|
// archives.
|
|
const WhiteoutMetaPrefix = WhiteoutPrefix + WhiteoutPrefix
|
|
|
|
// WhiteoutLinkDir is a directory AUFS uses for storing hardlink links to other
|
|
// layers. Normally these should not go into exported archives and all changed
|
|
// hardlinks should be copied to the top layer.
|
|
const WhiteoutLinkDir = WhiteoutMetaPrefix + "plnk"
|
|
|
|
// WhiteoutOpaqueDir file means directory has been made opaque - meaning
|
|
// readdir calls to this directory do not follow to lower layers.
|
|
const WhiteoutOpaqueDir = WhiteoutMetaPrefix + ".opq"
|