3 ms·
It's fully open source. I mean yes it uses llama.cpp without giving it credit. But why run it in a VM?
by nialv7 2y ago
It's fully open source. I mean yes it uses llama.cpp without giving it credit. But why run it in a VM?
- a12k 2y agoIt severely over-permissions itself on my Mac.
- deleted 2y ago[deleted]
- super_mario 2y agoCan you please elaborate? How are you running ollama? I just build it from source and have written a shell script to start/stop it. It runs under my local user account (I should probably have its own user) and is of course not exposed outside localhost.
- celeritascelery 2y agoI have never had it request any permissions
- _w1tm 2y agoJust install it from Brew and run the service in a separate terminal tab.
- instagary 2y agoIsn't there a clause in MIT that says you're required to give credit? Also, I didn't know a YC company which started it: https://www.ycombinator.com/companies/ollama https://www.ycombinator.com/companies/ollama.
- krowek 2y ago> But why run it in a VM? Because you don't execute untrusted code in your machine without containerization/virtualization. Don't you?
- adastra22 2y agoEvery single day. There's just too much good software out there, and life is too short to be so paranoid.
- Aurornis 2y agoThe question was asking why it’s untrusted code, not why you run untrusted code in a VM. There are a lot of open-source tools that we have to trust to get anything done on a daily basis.