Aleksei SviridkinandClaude
4a45dc998a
Add comprehensive troubleshooting documentation for inotify instance limit
errors that cause Jellyfin crashes in environments with many containers.
Changes:
- Add Troubleshooting section to README with inotify limits explanation
- Document proper solution: increase kernel limits via sysctl
- Provide workaround for managed clusters: DOTNET_USE_POLLING_FILE_WATCHER
- Add commented example in values.yaml for easy copy-paste
- Update Chart version from 2.5.0 to 2.5.1
- Add Artifact Hub changelog annotation
The proper solution is to increase inotify limits on Kubernetes nodes:
```bash
sysctl -w fs.inotify.max_user_instances=512
```
For managed Kubernetes where node access is restricted, users can use the
polling workaround (less efficient but functional):
```yaml
jellyfin:
env:
- name: DOTNET_USE_POLLING_FILE_WATCHER
value: "1"
```
This addresses the crash issue mentioned in #64.
Fixes: #64
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
17 lines
419 B
YAML
17 lines
419 B
YAML
apiVersion: v2
|
|
name: jellyfin
|
|
description: A Helm chart for Jellyfin Media Server
|
|
type: application
|
|
home: https://jellyfin.org/
|
|
icon: https://jellyfin.org/images/logo.svg
|
|
keywords:
|
|
- jellyfin
|
|
- media
|
|
- self-hosted
|
|
version: 2.5.1
|
|
appVersion: 10.11.2
|
|
annotations:
|
|
artifacthub.io/changes: |
|
|
- kind: added
|
|
description: Add troubleshooting documentation for inotify instance limits with workaround example
|