about summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorgithub-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>2021-12-04 18:01:05 +0000
committerGitHub <noreply@github.com>2021-12-04 18:01:05 +0000
commitd4c54e7f612a1cdac6396d7911139249299cf390 (patch)
tree734e2068abf627454b99d1c269319a0a3002d68f /doc
parenta3ef129c42a7a6908043b8445081e3f5e91c1dc5 (diff)
parent14895ade52f7c3edba635ded0238939f3417b42d (diff)
downloadnixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar.gz
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar.bz2
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar.lz
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar.xz
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.tar.zst
nixlib-d4c54e7f612a1cdac6396d7911139249299cf390.zip
Merge master into staging-next
Diffstat (limited to 'doc')
-rw-r--r--doc/builders/images/dockertools.section.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/builders/images/dockertools.section.md b/doc/builders/images/dockertools.section.md
index bfe1d17a6067..7ff4b2aeb369 100644
--- a/doc/builders/images/dockertools.section.md
+++ b/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.