[BUG] Mage docker container doesn't start with bind mounts on Windows #454
Labels
bug
bug
Effort - Medium
Effort - Medium
Frequency - EveryTime
Frequency - EveryTime
Priority - Later
Priority - Later
Reach - Some
Reach - Some
Severity - S3
Severity - S3
Describe the bug
then it just exits with status 139 according to docker desktop.
To Reproduce
Steps to reproduce the behavior:
Run this compose on Windows 10 with docker desktop 4.26.1, directories ./mg_lib, ./mg_log and ./mg_etc have been created before running docker compose up
Expected behavior
Mage should start like it does when the compose defines volumes instead of bind mounts.
Screenshots
The text was updated successfully, but these errors were encountered: