cannot create directory '/home/node/.cache': Permission denied

[ido-nl]

Don know what I am doing wrong. I keep getting this error
I use these user/group id's for all my dockers, they all work fine.

cinephage  | Running as UID=1024 GID=101
cinephage  | Checking directory permissions...
cinephage  | Directory permissions OK
cinephage  | mkdir: cannot create directory '/home/node/.cache': Permission denied
cinephage  | Indexer definitions already present (8 files)
cinephage  | Downloading Camoufox browser (first run only, ~80MB)...
cinephage exited with code 0

What am I doing wrong?

[mikesellt]

This same issue was closed before, but I do think this needs some further info. Are you running on a Synology NAS by chance? Mine was running fine and not referencing the .cache folder at all until I pulled the latest release, and then I started getting the same errors you're experiencing. What I did to fix it was add another volume to redirect the /home/node/.cache folder to another one on the host. When running, Cinephage seems to reference the /home/node/.cache and just plain /.cache for different things, so I just created one for each. Here's my full volume section of my docker compose:

volumes:
# Persist the SQLite database and settings
- ./data:/app/data
# Persist logs
- ./logs:/app/logs
# Mount your media library (adjust the host path on the left)
- ./media:/media
- ./cache:/home/node/.cache:rw
- ./camoufoxcache:/.cache:rw

I have /home/node/.cache pointed to /cache on the host, and I created a new one for the /.cache which is pointed to /camoufoxcache on the host. This is what worked for me. Can you try that? If not, can you show your compose file so we can see how you're set up?

[MoldyTaint]

I'll look into this - I am off of work today.

We've been testing different things with Camoufox which is used for bypassing cloudflare things.

[MoldyTaint]

Alright, finally got some of this shit figured out better.

The issue was Camoufox (the browser we use for bypassing Cloudflare) was trying to write to /home/node/.cache, but when you run with custom PUID/PGID that directory doesn't exist or has wrong permissions.

What changed:

• Set HOME=/app so everything stays in the app folder where it belongs
• Moved Camoufox cache from /home/node/.cache to /app/.cache/camoufox
• Fixed the file browser API to not use the home directory

Now everything (data, logs, cache) stays in /app and works with whatever UID/GID you may use.

@mikesellt thanks for the workaround in the meantime - that volume mount approach was clutch while we are still messing with this.

Still leaving this open in case I'm just stupid

[mikesellt]

So do I need to add HOME=/app as an environment variable or other setting? I have pulled the latest, and I'm not quite sure what settings I need to change now, and I'm facing the same problem as before.

[keonramses]

@ido-nl, are you on synology? Also please post your compose.

[ido-nl]

@keonramses I am indeed using a Synology NAS. Thank you for all the replies and suggestions.
Silly, why didnt I think of this, mapping the internal cache folder to a folder on host system.

But thats not needed anymore? I just pulled the latest image, but that fix isnt there yet. Perhaps thats the wrong image to pull. I'll investigate further after dinner.

[keonramses]

You do not need to mount the cache folder, but if you do please ensure that you create the base folder for it on your host and make sure the UID:GID you set via the env var is correct and that you do not use the user flag.

I did have the same issue last night when trying to update the image on DSM. Stop the project and change image tag from 'latest' to 'sha-37738bb' to force a repull or you can remove unused images after stopping and removing the container.

If you have any issues using the new image, please post your compose.

[ido-nl]

Using PUBLIC_APP_VERSION sha-37738bb
Still have the same issue unfortunately

services:
  cinephage:
    image: ghcr.io/moldytaint/cinephage:sha-37738bb
    container_name: cinephage
    restart: unless-stopped
    init: true # Use tini to prevent zombie browser processes
    user: '1024:101'
    security_opt:
      - no-new-privileges:true
    ports:
      - '6223:3000'
    volumes:
      - /volume1/docker/cinephage/data:/app/data # Database and config (auto-created)
      - /volume1/docker/cinephage/logs:/app/logs # Log files (auto-created)
      - /volume1/public/1.Media:/media # Your media library
    environment:
      # Required if accessing via IP/hostname other than localhost
      - ORIGIN=http://192.168.1.3:6223
      # Timezone for scheduled tasks (timedatectl list-timezones)
      - TZ=Europe/Amsterdam

[keonramses]

Remove the user flag and pass your UID:GID via the env vars. The userflag only makes sense if you are running rootless docker.

services:
  cinephage:
    image: ghcr.io/moldytaint/cinephage:sha-37738bb
    container_name: cinephage
    restart: unless-stopped
    init: true # Use tini to prevent zombie browser processes
    security_opt:
      - no-new-privileges:true
    ports:
      - '6223:3000'
    volumes:
      - /volume1/docker/cinephage/data:/app/data # Database and config (auto-created)
      - /volume1/docker/cinephage/logs:/app/logs # Log files (auto-created)
      - /volume1/public/1.Media:/media # Your media library
    environment:
      # Required if accessing via IP/hostname other than localhost
      - ORIGIN=http://192.168.1.3:6223
      # Timezone for scheduled tasks (timedatectl list-timezones)
      - TZ=Europe/Amsterdam
      - PUID=1024
      - PGID=101

Please read the comment here: #96 (comment), the data and log files are now being stored in /config. If you do not have existing data remove the mountpoints from your compose:

- /volume1/docker/cinephage/data:/app/data # Database and config (auto-created)
- /volume1/docker/cinephage/logs:/app/logs # Log files (auto-created)
      

And mount this instead:

- /volume1/docker/cinephage/config:/config

[ido-nl]

Yeahhh, I feel like having a party now. This solved it indeed. I must have missed the /config mapping, thanks for pointing this out and for helping.

[keonramses]

I am glad to hear that. Also, not your fault. This was added last night. We do apologize for the confusion. Cinephage is in very active development and things tend to break. We are hoping to get a stable version out once we have fixed some minor bugs and enchanced the core features satisfactorily. Please feel free to report any issues you come across. Thank you.