Open curtislisle opened 2 years ago
In the docker-compose.yml file, under the minio service declaration, there is a line that sets the tty
property; if you toggle the boolean value found there, that may fix this problem.
Switching the default to tty: false did indeed fix the problem when running under MacOS. I did not have to make this change on my Ubuntu 20.04 system.
The issue itself may lie in the minio image version you're using. We ran into this issue in the past with a specific version of minio, documented here. If your minio image versions are different between your Ubuntu and MacOS machines, pulling the corresponding image on your MacOS machine might be worth a shot.
I am unable to run the multinet-api on MacOS 10.15.7; docker-compose 1.29.2
All the services come up, but there are communication errors associated with what seems to be the minio container Here is an excerpt of the error dump: