Blake Mizerany
Blake Mizerany
Are you still seeing this issue with the latest release of Ollama? We are unable to reproduce with a similar environment. If the issue persists, can you run with `OLLAMA_DEBUG=1`...
Ollama keeps a cache of your already download models under `~/.ollama` or `$OLLAMA_MODELS` if set. Ollama is currently compatible with Docker Registry, but we do not guarantee it will remain...
This is wonderful! Thank you, @jesseclin. If you're still open to posting a PR, please do!
I'm going to close this out. Looking forward to your PR! Please feel free to reference this issue in the PR.
This seems to be fixed in the latest release. Using your prompt and image I'm getting: ``` >>> /Users/bmizerany/Desktop/303718891-41a5f112-580c-4e58-beb6-e2d807bd95e0 (1) ... .png Added image '/Users/bmizerany/Desktop/303718891-41a5f112-580c-4e58-beb6-e2d807bd95e0 (1).png' The image you've provided...
@jianliao Ive reopened and will look into further.
Manually editing the unit files is not our recommended approach. Please see https://github.com/ollama/ollama/blob/main/docs/faq.md#setting-environment-variables-on-linux Closing, but please reopen and update if issues persist.
@SinanAkkoyun Can you confirm you have an empty `~/.ollama/models` directory?
@DarkCat5501 @XujieYuan Can either of you provide some simple steps / script to reproduce? I'm unable to reproduce this, but maybe I'm missing something?
Is it possible you're all seeing this while running two `ollama serve`s at the same time? If so, that may explain models being clobbered.