LAB-linuxserver/cstate
1
0
Fork 0
mirror of https://github.com/linuxserver/cstate.git synced 2026-02-20 07:55:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #119 from linuxserver/new-custom-files

Browse Source 
Custom files notification
This commit is contained in:
Eric Nemchik 2022-08-28 15:22:13 -05:00 committed by GitHub
commit 5ecf942573
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 35 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
content/issues/2022-08-29-custom-files.md Normal file
View File

@ -0,0 +1,35 @@
---
title: 'Notification: Changes For Custom Scripts & Services'
date: '2022-08-29 12:00:00Z'
informational: true
affected:
- 'Notifications'
- 'custom-files'
- 'custom-services'
section: issue
---
We have long supported [customizing our containers](https://www.linuxserver.io/blog/2019-09-14-customizing-our-containers) via scripts and services as a simple way for users to add their own logic and packages to a container without having to modify the Dockerfile and maintain a local build of the image. As part of the broader refresh of our base images, which has already made changes to the way that [mods work](https://info.linuxserver.io/issues/2022-08-27-mods/), we are also making changes to custom files and services.
### Custom Files
These now reside in `/custom-cont-init.d` instead of under `/config/custom-cont-init.d` which allows us to decouple them from our permissions logic, and means we no longer have to create the folders even if people aren't using them. Beyond the change in location everything else remains the same - the folder and files need to be owned by root, the files need to be chmod `+x` and are executed in name order.
### Custom Services
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.