Cannot start openvidu 2.30 after setting up recording

[ao-Barbosa]

Describe the bug
After following the instructions on the "On premises Docs", starting the containers (compose up) leads to errors on the server container.

2024-11-14 08:49:43   =======================================
2024-11-14 08:49:43   =       LAUNCH OPENVIDU-SERVER        =
2024-11-14 08:49:43   =======================================
2024-11-14 08:49:16 Error: Unable to access jarfile openvidu-server-*.jar

Expected behavior
After running docker compose up -d the services should be running.

Wrong current behavior
The container fails to start because there seems to be some file (openvidu-server-*.jar) missing.

OpenVidu tutorial where to replicate the error

1. On a windows machine, enter wsl, create and navigate to a folder
2. Setup:
   2.1. curl https://s3-eu-west-1.amazonaws.com/aws.openvidu.io/install_openvidu_latest.sh | bash
   2.2. cd openvidu
   2.3. Setup your .env file
3. Run ./openvidu start or docker compose up -d

Up until here, i can start and everything runs as expected

4. On your .env file, setup "OPENVIDU_RECORDING" to true and setup any folder different from default as "OPENVIDU_RECORDING_PATH"
5. Run ./openvidu restart or docker compose down & docker compose up -d
6. No longer runs.

Screenshots

Additional context
This has been tested on three different machines with varying configurations, from very high end to mid workstation.

[cruizba]

@ao-Barbosa is this only happening when you enable recordings? The only possible recording path to use is /opt/openvidu/recordings, other paths may fail. Does it work with the default recording path?