Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:329: starting container process caused "permission denied": unknown

docker-compose --profile "*" up -d
[+] Running 12/14
✔ Network docker_coze-network Created 0.0s
⠏ Container coze-mysql Starting 90.9s
✘ Container coze-minio Error 90.9s
✔ Container coze-etcd Healthy 5.9s
⠏ Container coze-nsqlookupd Starting 90.9s
✔ Container coze-elasticsearch Started 0.4s
✔ Container coze-mysql-setup-schema Created 0.0s
✔ Container coze-mysql-setup-init-sql Created 0.0s
✔ Container coze-nsqadmin Created 0.0s
✔ Container coze-nsqd Created 0.0s
✔ Container coze-minio-setup Created 0.0s
✔ Container coze-milvus Created 0.0s
✔ Container coze-redis Created 0.0s
✔ Container coze-server Created 0.0s
Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:329: starting container process caused "permission denied": unknown

Start by rerunning docker-compose --profile "*" up -d and focus on the coze-minio container, which reports the OCI runtime permission error. Inspect the Docker daemon and container runtime output to identify the failing permission boundary. Done means the affected containers start successfully with the documented compose command.

Written by the indexing model from the issue text.