Kong fails to start with permissions error on kong.yaml

[point-source]

Bug report

Describe the bug

When starting the local development environment with supabase start, the Kong container fails to start:

stack traceback:
[C]: in function 'error'
/usr/local/share/lua/5.1/kong/init.lua:490: in function 'init'
init_by_lua:3: in main chunk
nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong/init.lua:490: error parsing declarative config file /var/lib/kong/kong.yml:
/var/lib/kong/kong.yml: Operation not permitted

When checking the supabase/.temp/kong.yml file, it appears to have the correct permissions:

$ ls -hal supabase/.temp/
total 8
drwxr-xr-x 3 user staff 96B Feb 15 14:22 .
drwxr-xr-x 7 user staff 224B Feb 15 14:27 ..
-rw-r--r-- 1 user staff 2.8K Feb 15 14:22 kong.yml

I even made the whole supabase directory as permissive as possible (chomd -R 777 supabase) and tried again without success:

$ ls -hal supabase/.temp/
total 8
drwxrwxrwx 3 user staff 96B Feb 15 14:47 .
drwxrwxrwx 7 user staff 224B Feb 15 14:47 ..
-rwxrwxrwx 1 user staff 2.8K Feb 15 14:47 kong.yml

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Start supabase
   $ supabase start
2. Try to access the API and see that it does not respond properly:
   $ curl http://localhost:54321
3. Observe the kong container logs and see the traceback

Expected behavior

I expect the development environment to start and the APIs to be available

System information

• OS: macOS 12.1
• Version of supabase-cli: 0.17.3
• Version of Docker: 20.10.12, build e91ed57

Additional context

I also tried to steps on this similar issue without success

[point-source]

I figured it out. Turns out it was the macOS permissions system rather than the file system's permissions. I had to grant Docker "Full Disk Access" in System Preferences > Security.

More info about this here: https://stackoverflow.com/questions/58482352/operation-not-permitted-from-docker-container-logged-as-root