Skip to content

Commit e3a4dd5

Browse files
committed
doc/faq: fix markdown
1 parent 917b08d commit e3a4dd5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ environment.systemPackages = [ (
112112
) ];
113113
```
114114

115-
# Can I include my host's `<nixpkgs>` channel when building the VM?
115+
## Can I include my host's `<nixpkgs>` channel when building the VM?
116116

117117
Use the following configuration if you build your MicroVM with
118118
`--impure` from channels, not Flakes:
@@ -123,7 +123,7 @@ nix.nixPath = [
123123
];
124124
```
125125

126-
# How do I let the `microvm` user access block devices?
126+
## How do I let the `microvm` user access block devices?
127127

128128
You can re-add the following line to your host's NixOS configuration
129129
which was removed from microvm.nix:
@@ -136,7 +136,7 @@ The more secure solution would be writing custom
136136
`services.udev.extraRules` that assign ownership/permissions to the
137137
individually used block devices.
138138

139-
# My virtiofs-shared sops-nix /run/secrets disappears when the host is updated!
139+
## My virtiofs-shared sops-nix /run/secrets disappears when the host is updated!
140140

141141
A workaround may be setting `sops.keepGenerations = 0;`, effectively
142142
stopping sops-nix from ever removing old generations in

0 commit comments

Comments
 (0)