Bug: --path Option Broken When Pointing to a Folder

[gorkem]

Contact Details

No response

What happened?

When attempting to start the llamafile server with the --path option pointing to a specific folder, the server fails to serve the UI correctly, resulting in a 404 error.

Setting --path to a folder seems to be broken.
I was trying to test against the latest llama.cpp UI with a command like

./llamafile --server --model mymodel.gguf --path /path-to-latest/llama.cpp/ui/

I can see on the log

{"function":"log_server_request","level":"INFO","line":2766,"method":"GET","msg":"request","params":{},"path":"/","remote_addr":"127.0.0.1","remote_port":65160,"status":404,"tid":"4365993184","timestamp":1728834877}

Version

llamafile v0.8.13

What operating system are you seeing the problem on?

Mac

Update (Oct 14 2024):

Reading a bit more I realized SECCOMP sandboxing was enabled and indeed setting --unsecure fixes the issue. I think the issue is still valid since --path is broken without disabling sandboxing. However, severity can be lower since a workaround exist.