I hope that we haven’t given up on getting it to run in Docker. I was really excited to work on this project but like everyone else after installing I can’t get the Ollama pull down to populate. Previously I was able to get OpenAI to work but with this last update that no longer works either.
I’m looking forward to contributing as soon as I can get it up and running.
I can tell you what that is and why it will be hard to fix.
Its SharedArrayBuffer.
Its used for efficient communication between WebAssembly and threads in general.
You get speed at a cost of possible side channel attacks.
This restriction is enforced because SharedArrayBuffer enables high-resolution timers that can potentially be exploited in side-channel attacks like Spectre
That is why it is restricted to https and cross origin isolation.
In theory you could remove ShareArrayBuffer and just send/copy things, it will be slower.
But I don’t think we can do that as that requirement is in closes source part of Bolt called WebContainers that simulate full stack javascript environment to run apps in.
Sharing this as there could be motivated and talented people here to try and find solutions.
One issue that returns all the time is that WebContainers are closed sourced and owned by StackBlitz so we can’t really change much about them. And we may need to find a way to replace them with something open source like WebVM or Wasmer or something else.
May be replace them with Docker itself.
But it should be optional change, so those who are happy with WebContainer use them, and those who like other options can switch.
Its a large project.
There could be other solutions, in how to connect to ollama from docker.
My plans are different though. I want to allow hosted version to connect to localhost. I already tested with LM Studio that its possible in theory.
And this way I want just to remove need for most people to setup anything at all, just install ollama or lmstudio and use hosted website. No dockers no problems 
Does not mean I am against Docker support, just find it to be power user path. We need to support it, and there are many other things to do too.
I hope this information helps to save time to some investigating this.