From 4409ab606a3510496cb2330f1d0513ce0c09a0be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adri=C3=A1n=20Parilli?= Date: Wed, 13 Dec 2023 18:18:02 -0400 Subject: [PATCH] Fixed link to header --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ae6ea80..11b25cc 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ Refer to the [source code](https://github.com/abbbi/virtnbdbackup) for better un But in some operating systems, `/run` and `/var/run` are still separated folders. Under this scenario you need to bind mount with `-v /var/run:/run` And most likely, you will need to mount with either `-v /var/lock:/run/lock` or `-v /var/run/lock:/run/lock` in order to run this container correctly. - If you're in trouble with this, read source [FAQ](https://github.com/abbbi/virtnbdbackup#faq) and create a [persistent container](###persistent-container) in order to debug, and get the correct bind mounts that work for your main host. + If you're in trouble with this, read source [FAQ](https://github.com/abbbi/virtnbdbackup#faq) and create a [persistent container](#persistent-container) in order to debug, and get the correct bind mounts that work for your main host. - Virtnbdbackup and virtnbdrestore create sockets for backup/restoration jobs tasks at `/var/tmp`. Ensure to always add a bind mount with `-v /var/tmp:/var/tmp`