From 4dcd29720dd28766fd3dd434d47a657e3d74f782 Mon Sep 17 00:00:00 2001 From: TheSpad Date: Sun, 28 Aug 2022 17:16:04 +0100 Subject: [PATCH] Add mount notes --- content/issues/2022-08-29-custom-files.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/content/issues/2022-08-29-custom-files.md b/content/issues/2022-08-29-custom-files.md index 3cf68b98..6de6820c 100644 --- a/content/issues/2022-08-29-custom-files.md +++ b/content/issues/2022-08-29-custom-files.md @@ -19,3 +19,17 @@ These now reside in `/custom-cont-init.d` instead of under `/config/custom-cont- Similar to custom files, these now reside in `/custom-services.d` instead of under `/config/custom-services.d`. Beyond the change in location everything else remains the same - the folder and files need to be owned by root, and the service files need to be chmod `+x. The old custom locations will continue to work for a while to provide time for users to migrate but will generate warnings in the logs, as well as writing files to the old locations to notify users of the changes. We will post another notice before we remove the legacy locations entirely. + +### Mounting Paths + +Because these new locations are outside of `/config` you will need to mount them like any other volume if you wish to make use of them. e.g. `-v /home/foo/appdata/my-custom-files:/custom-cont-init.d` if using the Docker CLI or + +```yaml +services: + bar: + volumes: + - /home/foo/appdata/bar:/config + - /home/foo/appdata/my-custom-files:/custom-cont-init.d +``` + +if using compose. Where possible, to improve security, we recommend mounting them read-only (`:ro`) so that container processes cannot write to the location.