Docker容器内Buildozer权限拒绝问题求助（MacOS环境）

阿华AIGC实验室

2026-5-27

Fixing Permission Denied Error When Packaging Kivy Android App via Docker on macOS

Hey there! Let's work through that permission denied error you're hitting while using Docker to build your Kivy Android app on macOS. Based on your setup and command, here are some practical steps to resolve this:

Check local directory permissions & macOS security settings
First, make sure your project directory has proper read/write permissions for your user. Run this command on your local machine:
```
chmod -R 755 /Users/saurabhshrivastava/saurabh/kivy/practice/test
```
Also, head to System Preferences > Security & Privacy > Privacy > Files and Folders and ensure Docker Desktop is allowed access to your project directory—macOS often blocks app access to user folders by default.
Match container user to your local UID/GID
A common issue with Docker volumes on macOS is mismatched user IDs between your local system and the container. Run the Docker command with your local user's UID/GID to ensure the container process has the right permissions to access the mounted files:
```
sudo docker run --privileged -u $(id -u):$(id -g) \
  -v /Users/saurabhshrivastava/saurabh/kivy/practice/test:/buildozer/ \
  -v /etc/udev/rules.d/:/etc/udev/rules.d/ \
  tshirtman/buildozer buildozer android debug
```
Remove unnecessary udev mount (MacOS doesn't use udev)
macOS doesn't have a udev system, so mounting /etc/udev/rules.d/ to the container is likely unnecessary and could be causing permission conflicts. Try running the command without that volume mount:
```
sudo docker run --privileged -u $(id -u):$(id -g) \
  -v /Users/saurabhshrivastava/saurabh/kivy/practice/test:/buildozer/ \
  tshirtman/buildozer buildozer android debug
```
Verify your buildozer.spec file permissions
Ensure your project's buildozer.spec isn't set to read-only, which could block the build process from modifying it:
```
chmod 644 /Users/saurabhshrivastava/saurabh/kivy/practice/test/buildozer.spec
```
Capture the full error log for precise debugging
The output snippet you shared only shows the initial setup steps—actual permission errors are usually later in the log. Run this command to save the full log to a file, then look for lines containing "permission denied":
```
sudo docker run --privileged -u $(id -u):$(id -g) \
  -v /Users/saurabhshrivastava/saurabh/kivy/practice/test:/buildozer/ \
  tshirtman/buildozer buildozer android debug 2>&1 | tee buildozer_log.txt
```