diff options
Diffstat (limited to 'nixpkgs/doc/builders/images/dockertools.section.md')
| -rw-r--r-- | nixpkgs/doc/builders/images/dockertools.section.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/nixpkgs/doc/builders/images/dockertools.section.md b/nixpkgs/doc/builders/images/dockertools.section.md index bfe1d17a6067..7ff4b2aeb369 100644 --- a/nixpkgs/doc/builders/images/dockertools.section.md +++ b/nixpkgs/doc/builders/images/dockertools.section.md @@ -151,6 +151,12 @@ Create a Docker image with many of the store paths being on their own layer to i : Shell commands to run while creating the archive for the final layer in a fakeroot environment. Unlike `extraCommands`, you can run `chown` to change the owners of the files in the archive, changing fakeroot's state instead of the real filesystem. The latter would require privileges that the build user does not have. Static binaries do not interact with the fakeroot environment. By default all files in the archive will be owned by root. +`enableFakechroot` _optional_ + +: Whether to run in `fakeRootCommands` in `fakechroot`, making programs behave as though `/` is the root of the image being created, while files in the Nix store are available as usual. This allows scripts that perform installation in `/` to work as expected. Considering that `fakechroot` is implemented via the same mechanism as `fakeroot`, the same caveats apply. + + *Default:* `false` + ### Behavior of `contents` in the final image {#dockerTools-buildLayeredImage-arg-contents} Each path directly listed in `contents` will have a symlink in the root of the image. |