Is there an existing issue for this?
Current Behavior
The mStream v6 release has come out today. I've had a few users report error logs. I traced the issue and it's due two new rust binaries that were introduced. One binary scans the files for metadata and the other allows the server to playback audio. There's two potential issues that need to be addressed:
- The binaries need to be executable
- The binaries need to be compatible for Alpine
I'm looking into how to compile them for Alpine support. Any advice would be appreciated
Expected Behavior
The rust binaries can be executed by the NodeJS processes
Steps To Reproduce
Run the server. There will be some logs after boot saying the rust parser has failed. This is not a big issue because there is a fallback parser in NodeJS
Environment
- OS: Linux
- How docker service was installed: Uknown
CPU architecture
x86-64
Docker creation
Standard creation procedure as outlined in the readme
Container logs
Is there an existing issue for this?
Current Behavior
The mStream v6 release has come out today. I've had a few users report error logs. I traced the issue and it's due two new rust binaries that were introduced. One binary scans the files for metadata and the other allows the server to playback audio. There's two potential issues that need to be addressed:
I'm looking into how to compile them for Alpine support. Any advice would be appreciated
Expected Behavior
The rust binaries can be executed by the NodeJS processes
Steps To Reproduce
Run the server. There will be some logs after boot saying the rust parser has failed. This is not a big issue because there is a fallback parser in NodeJS
Environment
CPU architecture
x86-64
Docker creation
Standard creation procedure as outlined in the readmeContainer logs