Mounting does not work if files are located in a volume
- Lenguaje dominante
- Go
- Estrellas
- 30.8k
- Forks
- 613
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Description
I have all my projects in a macOS Volume `/Volumes/Projects`. When I try to start the container via docker compose I get an error
`Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/Volumes/Projects/PROJECT_PATH/docker/crontab" to rootfs at "/crontab": mount /Volumes/Projects/PROJECT_PATH/docker/crontab:/crontab (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type`
As I just figured out it's because of the location. If I move the files to i.e. `~/test` and start it there everything works fine. Is there a possibility via configuration i.e. to make that work?
### Version
Colima Version: 0.5.6
Lima Version: 0.17.2
Qemu Version: 8.1.1
### Operating System
- [ ] macOS Intel <= 12 (Monterrey)
- [ ] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [X] macOS M1 >= 13 (Ventura)
- [ ] Linux
### Output of `colima status`
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/matthiashamacher/.colima/default/docker.sock
### Reproduction Steps
1. Create a new volume in the macOS Disk Utility
2. Have a docker compose with mounted files
3. Start the containers via `docker compose up`
### Expected behaviour
Everything works all mounts can be established
### Additional context
_No response_
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.