Notifications custom-files custom-services
As we announced back in August, we have made changes to the locations that custom scripts and services are imported from. We are now starting the process of removing support for the old locations from our base images. This means that after the end of December 2022 we will no longer support running custom scripts and services from the legacy locations within the /config mount. Please note that it may take several days, or even a few weeks in some cases, for this change to propagate to all of our images.
These now reside in /custom-cont-init.d. The folder and files need to be owned by root, the files need to be chmod +x and are executed in name order.
Similar to custom files, these now reside in /custom-services.d. The folder and files need to be owned by root, and the service files need to be chmod +x.
Because these new locations are outside of /config you will need to mount them like any other additional volume if you wish to make use of them. e.g. -v /home/foo/appdata/my-custom-files/bar:/custom-cont-init.d:ro if using the Docker CLI or
services:
bar:
volumes:
- /home/foo/appdata/bar:/config
- /home/foo/appdata/my-custom-files/bar:/custom-cont-init.d:ro
if using compose. Where possible, to improve security, we recommend mounting them read-only (:ro) so that container processes cannot write to the location.
Please note that we do not support mounting folders for custom scripts and services if they sit within the same folder that you are mounting for /config. i.e.
- /home/foo/appdata/bar:/config
- /home/foo/appdata/bar/custom-stuff:/custom-cont-init.d
as this can cause you permissions problems.
Last updated: December 22, 2022 at 5:58 PM