[Bug]: File permissions on service stack configuration files after Coolify upgrade

[actraiser]

Error Message and Logs

After upgrading to the Coolify 4.0.0-Beta-384 , i also noticed that when restarting my Supabase Stack, it failed. The Container logs threw errors for both supabase-db and supabase-kong. Both complained about errors accessing configuration files (kong.yml and postgres.conf) - those files reside in /data/coolify/services/-the-id-/volumes/api and /data/coolify/services/-the-id-/volumes/db

I had to manually update the file permissions of the two files to make restarting the stack work again. Did any of the recent coolify updates change how configuration files bind by docker-compose stack are treated/stored? While I modified postgres.conf a lot in the past, i never touched kong.yml by the way.

-act

Steps to Reproduce

Restart an existing Supabase Service Stack under Beta 384

Example Repository URL

No response

Coolify Version

v4.0.0-beta.385

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.1 LTS