Mac docker install fails

aliasfox · February 18, 2025, 4:58pm

I think there’s an auth issue on your system, or the .git metadata is not being found. Can you try putting GIT_DISCOVERY_ACROSS_FILESYSTEM=1 before the docker compose to pass the parameter? Alternatively you could add it to the environment variable, etc.

docker run -e GIT_DISCOVERY_ACROSS_FILESYSTEM=1 dockerbuild

or

GIT_DISCOVERY_ACROSS_FILESYSTEM=1 docker compose --profile development up

Depending on which method you are using.

yvesete · February 18, 2025, 5:35pm

did try

same result, nor error but not working

thecodacus · February 18, 2025, 5:52pm

can you try commenting out this line from the dockerfile ?

and then try building the image

yvesete · February 18, 2025, 6:37pm

I did comment out, built again and composed with

same result no error not working.

aliasfox · February 18, 2025, 7:21pm

I will test and document my process later, but I can’t test it right now. It should be quicker if I can troubleshoot my way through it.

yvesete · February 21, 2025, 3:20pm

I assume it did not work ?

aliasfox · February 21, 2025, 4:12pm

Actually, I could not replicate your issue but I’m not on Mac. So it appears to be a Mac specific issue and/or your specific setup/machine. Have you tried using npm install bolt.diy instead? I believe it’s still kind of beta but should work whereas the Docker method is failing for you.

yvesete · February 21, 2025, 4:29pm

Did not do up to know and I might consider it but I prefer a docker install. Otherwise I might get some issues with other packages. I wait until next release and try again with docker. So no bolt.diy for me right now.

aliasfox · February 21, 2025, 4:49pm

I personally don’t like Docker on Windows or Mac as it has weird side effects and overhead due to being virtualized. It’s only native to Linux and I still haven’t 100% made Linux my daily driver (40/60) because something always seems to bring me back to Windows. But bleeding edge AI stuff primarily works best on Linux and use Python. And I love Python already, so idk I just need the dedication to make the move.

And I’m sorry it didn’t work, still not sure why, but I’m really not a Mac user myself (though I’ve considered getting a M4 Mac Mini to run energy efficient local models as kind of a service).

leex279 · February 21, 2025, 4:54pm

@yvesete if just the building is the problem, try out the prebuild version, which you can see also in my stack:

github.com/leex279/bolt-diy-full-stack

docker-compose-nvidia.yml

main

networks:
  shared_network:
    driver: bridge

services:
  ollama:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: ollama
    ports:
      - "11434:11434"  # Maps Ollama service port to host
    runtime: nvidia
    networks:
      - shared_network  # Connects to the shared network
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia

This file has been truncated. show original

yvesete · February 22, 2025, 12:59pm

I tried it 4 days ago and it did not work (see above) if it is the same build?

leex279 · February 22, 2025, 1:02pm

It is the main branch. As always in docker, a start of the container, does not automatically pull the latest release. you need to pull it manually (at least for me in docker desktop (windows) is it like this.

Other than that I just saw that the latest main branch is not working with docker. It´s stuck in a endless loop. So, this BUG needs to be fixed first, before it can be used.

yvesete · February 22, 2025, 1:03pm

@aliasfox Well except the windows manager MacOs is nearly 100% Linux. I am running a couple of tiny Linux servers (Ubuntu) and docker on Linux and MacOs is running great without problems. I might try a npm install in a seperate conda environment.

yvesete · February 22, 2025, 1:05pm

@lex279 ah ok it seems that is exactly happening.
I try a npm install in a conda env.

yvesete · February 22, 2025, 1:37pm

tried it in a conda environment with pnpm and it is also exactly the same, no error but unusable same as before with docker install.

leex279 · February 22, 2025, 2:18pm

give it another try (from scratch/clean conda) and use NPM instead of PNPM. I remember one Mac here in another topic which it also not worked with pnpm, but npm.

aliasfox · February 22, 2025, 4:01pm

Not sure I understand why you are using a conda environment with NodeJS. Conda is intended for Python and I’m not sure if that is causing issues on it’s own.

aliasfox · February 22, 2025, 4:05pm

Yes and no. Mac OS is based on a version of Linux but not Linux strictly speaking. A lot of things will work the same but Docker is still virtualized in Mac. Not the same as on Linux…

yvesete · February 22, 2025, 7:25pm

that is true and with conda you have a point. I am so used to use it …

ok total fresh install without conda and gitclone not the zip file and it works except Ollama, is not choosable (not in list) allthough I have it in env.local with http://localhost:11434 and with docker it works that way maybe different without ?

leex279 · February 22, 2025, 7:47pm

The ollama url needs to be http://127.0.0.1:11434 instead of localhost.