1mkcomposefs(1) User Commands mkcomposefs(1)
2
3
4
6 mkcomposefs - create a composefs filesystem image
7
9 mkcomposefs SOURCE IMAGE
10
12 The composefs project uses EROFS image file to store metadata, and one
13 or more separate directories containing content-addressed backing data
14 for regular files.
15
16 mkcomposefs constructs the mountable “composefs image” using the source
17 as input. It can also create the backing store directory. Typically
18 the source is a directory, but with –from-file it can also be a file.
19
21 The provided SOURCEDIR argument must be a directory and its entire con‐
22 tents will be read recursively. The provided IMAGE argument will be a
23 mountable composefs image.
24
25 mkcomposefs accepts the following options:
26
27 --digest-store=PATH
28 This path will become a composefs “object store”. Non-empty
29 regular files in the SOURCEDIR will be copied (reflinked if pos‐
30 sible) into this target directory, named after their fsverity
31 digest. If possible, the added files will have fs-verity en‐
32 abled.
33
34 This directory should be passed to the basedir option when you
35 mount the image.
36
37 --print-digest
38 Print the fsverity digest of the composefs metadata file.
39
40 --print-digest-only
41 Print the fsverity digest of the composefs metadata file, but
42 don’t write the image. If this is passed, the IMAGE argument
43 should be left out.
44
45 --use-epoch
46 Use a zero time (unix epoch) as the modification time for all
47 files.
48
49 --skip-devices
50 Don’t add device nodes to the image.
51
52 --skip-xattrs
53 Don’t add xattrs to files in the image.
54
55 --user-xattrs
56 Only add xattrs with the “user.” prefix to files in the image.
57
58 --from-file
59 The source is a file in the composefs-dump(5) format. If the
60 specified file is “-”, the data is read from stdin.
61
63 composefs-info(1), mount.composefs(1), composefs-dump(5)
64
65 composefs upstream (https://github.com/containers/composefs)
66
67
68
69composefs mkcomposefs(1)