Got error while deploy with docker-compose after update to 5.0.0

[dickens88]

Describe the bug
Hi , i cloned the project with command git clone https://github.com/mitre/caldera.git --recursive , and i'm sure the magma have been downloaded in the plugins folder. But when i try to deploy with docker-compose, it got this error.

caldera-1  | Traceback (most recent call last):
caldera-1  |   File "/opt/venv/caldera/lib/python3.11/site-packages/aiohttp/web_urldispatcher.py", line 561, in __init__
caldera-1  |     raise ValueError("Not a directory")
caldera-1  | ValueError: Not a directory
caldera-1  | 
caldera-1  | The above exception was the direct cause of the following exception:
caldera-1  | 
caldera-1  | Traceback (most recent call last):
caldera-1  |   File "/usr/src/app/server.py", line 260, in <module>
caldera-1  |     run_tasks(services=app_svc.get_services(), run_vue_server=args.uiDevHost)
caldera-1  |   File "/usr/src/app/server.py", line 78, in run_tasks
caldera-1  |     loop.run_until_complete(RestApi(services).enable())
caldera-1  |   File "/usr/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
caldera-1  |     return future.result()
caldera-1  |            ^^^^^^^^^^^^^^^
caldera-1  |   File "/usr/src/app/app/api/rest_api.py", line 32, in enable
caldera-1  |     self.app_svc.application.router.add_static('/assets', 'plugins/magma/dist/assets/', append_version=True)
caldera-1  |   File "/opt/venv/caldera/lib/python3.11/site-packages/aiohttp/web_urldispatcher.py", line 1136, in add_static
caldera-1  |     resource = StaticResource(
caldera-1  |                ^^^^^^^^^^^^^^^
caldera-1  |   File "/opt/venv/caldera/lib/python3.11/site-packages/aiohttp/web_urldispatcher.py", line 563, in __init__
caldera-1  |     raise ValueError(f"No directory exists at '{directory}'") from error
caldera-1  | ValueError: No directory exists at '/usr/src/app/plugins/magma/dist/assets'
caldera-1 exited with code 1

Is this magma mandatory for this version? or is it possbile to disable this part somehow?

[individual10121]

I ran into a similar issue. I had to go into the magma directory and run the following:
npm install npm run build

Then I was able to get it to launch. But now I have an issue where no OS is listed in the deploy agents menu