Replies: 1 comment
-
Closing the discussion in favor of this issue https://github.com/supabase/supabase/issues/15040 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
On local-development there seems to be an issue with filesystem permissions over the
deno
Docker container.When trying to access an Edge Function file, Deno fails with
error: Permission denied (os error 13)
.I
docker-exec -it $deno_container bash
intodocker ps | grep deno
and can see that:id
returns the userdeno
, having UID & GID equal to1993
ls -la /home/deno/functions/my-function/index.ts
shows onwer UID and group GID as equal to1000
1000
is usually corresponding to thedocker
user; when it appears in a container usually is the sign of some volume mount of some sort.Is this the case?
I saw the
/app/Dockerfile
simply copies the files, from localhost to the container, but I don't see why they should have this mismatching file permissions.Can somebody check in their working docker local-dev if the 2 commands above return the same results as me?
At the moment I am unable to test functions locally.
What could be causing the error?
What can I try to restore the correct functionality?
Could this be a bug?
More info
I run:
supabase start
supabase functions serve my-function
--debugit outputs:
Additionally
supabase stop
andstart
again to see if it would reset the image & containers, but nothing changedchmod 777
theindex.ts
file inside the container but userdeno
has no rights to do so andsudo
is not available.Beta Was this translation helpful? Give feedback.
All reactions