Describe the bug
react-scripts start
/usr/bin/env: 'node': Text file busy
mrs-frontend | error Command failed with exit code 126.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The container does start, but I assume something is wrong. I apologise as I'm not sure if this is causing any of my issues, or any issues at all, but it looks like something that would be easy to fix and I'm sure it's there for some reason.
I also note this - no idea if it's related:
Note that the development build is not optimized.
To create a production build, use yarn build.
To Reproduce
Steps to reproduce the behavior:
Start frontend container
Expected behavior
No error message
Log files
Attached
Environment (please complete the following information):
Device type: Mac Pro 16 M1 Pro
OS: Mac OS Sonoma
Mycroft-core version: Latest Docker
Other versions:
Additional context
Only change I've made is to get this all to run on port 5001, which is required on a Mac.
Please think carefully about whether you have modified anything in Mycroft's code or configuration files. If so, can you reproduce this on a clean installation of Mycroft? Many "bugs" turn out to be non-standard configuration errors.
logs.txt
Describe the bug react-scripts start /usr/bin/env: 'node': Text file busy mrs-frontend | error Command failed with exit code 126. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The container does start, but I assume something is wrong. I apologise as I'm not sure if this is causing any of my issues, or any issues at all, but it looks like something that would be easy to fix and I'm sure it's there for some reason.
I also note this - no idea if it's related: Note that the development build is not optimized. To create a production build, use yarn build.
To Reproduce Steps to reproduce the behavior: Start frontend container
Expected behavior No error message
Log files Attached
Environment (please complete the following information):
Additional context Only change I've made is to get this all to run on port 5001, which is required on a Mac.
Please think carefully about whether you have modified anything in Mycroft's code or configuration files. If so, can you reproduce this on a clean installation of Mycroft? Many "bugs" turn out to be non-standard configuration errors. logs.txt