Cannot create directory '/backend/out/...': Permission denied using macOS

[cboiangiu]

Encountered this while using release 0.0.2 on macOS 14.2.1 (M1) with OrbStack 1.4.3.

This is my entrypoint.sh:

#!/bin/sh
set -e

OUTDIR="/backend/out"

cd /backend

cp -r /vosk /backend/out/

cp -r /nerd-dictation /backend/out/

This is the error encountered:

 => => writing image sha256:1c6698adc262a63cc3d1ba0de529cdbfa23753ca5961aaf780c89e00c5677efa                                                                                                                      0.0s
 => => naming to docker.io/library/decky-dictation                                                                                                                                                                0.0s

What's Next?
  View a summary of image vulnerabilities and recommendations → docker scout quickview
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
cp: cannot create directory '/backend/out/vosk': Permission denied
Error: Failed to build backend. There might be more information in the output above.

Caused by:
    child status was: exit status: 1

Tried to cp the folders into out2 just to test and that seems to work without any problems.

[AAGaming00]

This is an issue with your container runtime. We only support official podman and docker.

[cboiangiu]

@AAGaming00 Funny you mentioned that 😅. I was using docker in the beginning and the same issue happened there. I have moved onto OrbStack to give it a try as well since the PR that added the macOS build used it, but unfortunately it just had the same issue.

I have been successful in getting a build using docker and the previous build script I've been using. This leads me to believe that this is not an issue with the runtime used (docker).

I will use docker going forward in the hopes that we can find a fix for this issue.

Edit: Just gave it another try using docker. Same issue. cp: cannot create directory '/backend/out/vosk': Permission denied

[AAGaming00]

odd, I've used the cli on Linux and it builds fine with docker

[xfangfang]

I encountered a similar problem on m2 mac. The conclusion is: do not use sudo to run cli/decky

If you have previously used sudo to run, you may need to run the following command in the project root directory to fix it:

sudo rm -rf ./out
sudo rm -rf ./backend/out
sudo rm -rf /tmp/decky
sudo rm -rf /tmp/output
sudo chown $USER -R ~/.docker/buildx/activity

[cboiangiu]

@xfangfang Just gave this a try, but unfortunately it just gives the same error: cp: cannot create directory '/backend/out/vosk': Permission denied. Last command had a small typo: sudo chown -R $USER ~/.docker/buildx/activity.
Could you please give this PR a try on your m2 mac? Just trying to rule out any problems on my end, though I am not even sure where to begin troubleshooting this, since even different docker runtimes seem to give me the same issue.

[cboiangiu]

@xfangfang After a bit more digging, I think I understand what you meant about not sudo running cli/decky. I am using the build.sh from decky-plugin-template, which does seem to be using sudo.
After removing sudo, I now get this error ERROR: mkdir /Users/catalinboiangiu/.docker/buildx/refs/desktop-linux: permission denied.
Seems like my refs is owned by root:

drwx------  5 catalinboiangiu  staff  160 Mar 14 19:54 activity
-rw-------  1 catalinboiangiu  staff   48 Mar 14 19:24 current
drwx------  2 catalinboiangiu  staff   64 Feb 25 14:55 defaults
drwx------  2 catalinboiangiu  staff   64 Feb 25 14:55 instances
drwx------  5 root             staff  160 Feb 25 16:13 refs

I guess it is safe to chown this folder to my user?