You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🐛(minio) fix user permission error with Minio and Windows
With Minio Docker and Windows, the user ID needs
to be set to `0:0` to avoid permission issues.
This change ensures that the Minio container
runs with root privileges on Windows, which
is necessary for proper file access and management.
Copy file name to clipboardExpand all lines: docs/troubleshoot.md
-49Lines changed: 0 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,55 +83,6 @@ If you already have CRLF line endings in your local repository, the **best appro
83
83
git commit -m "✏️(project) Fix line endings to LF"
84
84
```
85
85
86
-
## Minio Permission Issues on Windows
87
-
88
-
### Problem Description
89
-
90
-
On Windows, you may encounter permission-related errors when running Minio in development mode with Docker Compose. This typically happens because:
91
-
92
-
-**Windows file permissions** don't map well to Unix-style user IDs used in Docker containers
93
-
-**Docker Desktop** may have issues with user mapping when using the `DOCKER_USER` environment variable
94
-
-**Minio container** fails to start or access volumes due to permission conflicts
95
-
96
-
### Common Symptoms
97
-
98
-
- Minio container fails to start with permission denied errors
99
-
- Error messages related to file system permissions in Minio logs
100
-
- Unable to create or access buckets in the development environment
101
-
- Docker Compose showing Minio service as unhealthy or exited
102
-
103
-
### Solution for Windows Users
104
-
105
-
If you encounter Minio permission issues on Windows, you can temporarily disable user mapping for the Minio service:
106
-
107
-
1.**Open the `compose.yml` file**
108
-
109
-
2.**Comment out the user directive** in the `minio` service section:
110
-
```yaml
111
-
minio:
112
-
# user: ${DOCKER_USER:-1000} # Comment this line on Windows if permission issues occur
113
-
image: minio/minio
114
-
environment:
115
-
- MINIO_ROOT_USER=impress
116
-
- MINIO_ROOT_PASSWORD=password
117
-
# ... rest of the configuration
118
-
```
119
-
120
-
3.**Restart the services**:
121
-
```bash
122
-
make run
123
-
```
124
-
125
-
### Why This Works
126
-
127
-
- Commenting out the `user` directive allows the Minio container to run with its default user
128
-
- This bypasses Windows-specific permission mapping issues
129
-
- The container will have the necessary permissions to access and manage the mounted volumes
130
-
131
-
### Note
132
-
133
-
This is a **development-only workaround**. In production environments, proper user mapping and security considerations should be maintained according to your deployment requirements.
0 commit comments