[BUG] ERROR:Exception: Not a directory '/sys/class/power_supply/' on Synology NAS

[matt08]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

After starting the Docker image, folding@home does not start. Errors appear in the logs: stdout [91m14:09:34:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m

Expected Behavior

folding@home starts correctly

Steps To Reproduce

1. I run the container via command line (with root privileges) or via GUI (Container Manager app in DSM)
2. I am checking the logs and see what I have attached. The mentioned errors appear in the logs constantly, but folding@home does not start correctly.

Environment

- OS: DSM 7.2-64570
- How docker service was installed: Installed by default in the system + available as a GUI via "Container Manager"

CPU architecture

x86-64

Docker creation

docker run -d \
  --name=foldingathome \
  -e PUID=1026 \
  -e PGID=100 \
  -e TZ=Etc/UTC \
  -e ACCOUNT_TOKEN=8dwDM.... \
  -e MACHINE_NAME=Name \
  -p 7396:7396 \
  -v /volume1/docker/fah:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/foldingathome:latest

### Container logs

```bash
2024/07/17 16:09:34	stdout	[91m14:09:34:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m
2024/07/17 16:09:33	stdout	[91m14:09:33:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m
2024/07/17 16:09:31	stdout	[91m14:09:31:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m
2024/07/17 16:09:30	stdout	[91m14:09:30:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m
2024/07/17 16:09:29	stdout	[91m14:09:29:ERROR:Exception: Not a directory '/sys/class/power_supply/'[0m
2024/07/17 16:09:29	stdout	[custom-init] No custom files found, skipping...
2024/07/17 16:09:29	stdout	**** The device /dev/dri/card0 does not have group read/write permissions, attempting to fix inside the container. ****
2024/07/17 16:09:29	stdout	**** The device /dev/dri/controlD64 does not have group read/write permissions, attempting to fix inside the container. ****
2024/07/17 16:09:29	stdout	**** permissions for /dev/dri/renderD128 are good ****
2024/07/17 16:09:29	stdout	    
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	Build-date: 2024-07-16T03:11:51+00:00
2024/07/17 16:09:29	stdout	Linuxserver.io version: 8.3.18-ls136
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	User GID:    100
2024/07/17 16:09:29	stdout	User UID:    1026
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	GID/UID
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	https://www.linuxserver.io/donate/
2024/07/17 16:09:29	stdout	To support LSIO projects visit:
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	Folding@home: https://foldingathome.org/about/donate/
2024/07/17 16:09:29	stdout	To support the app dev(s) visit:
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	   Brought to you by linuxserver.io
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	      ╚══════╝╚══════╝╚═╝ ╚═════╝
2024/07/17 16:09:29	stdout	      ███████╗███████║██║╚██████╔╝
2024/07/17 16:09:29	stdout	      ██║     ╚════██║██║██║   ██║
2024/07/17 16:09:29	stdout	      ██║     ███████╗██║██║   ██║
2024/07/17 16:09:29	stdout	      ██║     ██╔════╝██║██╔═══██╗
2024/07/17 16:09:29	stdout	      ██╗     ███████╗██╗ ██████╗
2024/07/17 16:09:29	stdout	
2024/07/17 16:09:29	stdout	───────────────────────────────────────
2024/07/17 16:09:29	stdout	usermod: no changes
2024/07/17 16:09:29	stdout	[migrations] no migrations found
2024/07/17 16:09:29	stdout	[migrations] started

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[nathang21]

+1 I have the exact same issue (and same config as OP).

Looks like a similar issue as outlined here in the forums (need an account to view) turned out to be a permissions issue with /sys which was "fixed" back in 2011, but this may be an issue with thie container image, going to try using the official container next (edit: looks like this hasn't been re-built in 2 years, so i'm not going to bother).

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[nathang21]

Not stale.

[aptalca]

/sys folder is a file based representation of kernel access. It doesn't come within our image. It comes from your host kernel.

I suspect it's an incompatibility with synology's super old kernels and the upstream project.

Nothing we can do on our end. I can't reproduce it on any of my systems.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity