[Self-Host] Docker Compose Build Stuck and Failing to Proceed in MacOS Orbstack Environment

[lukefan]

Describe the Issue
When running docker compose build, it gets stuck at sha256:06191ad9adfe70fa8e5472c59bda366508230e9d5d3ceef4cec4b118f1ceac5b 0B / 40.73MB and remains unresponsive for several hundred seconds. Multiple attempts have been made but the deployment always fails.
To Reproduce
Set up the environment in the orbstack environment on macOS.
Run the docker compose build command.
Observe that it gets stuck at the mentioned progress status and shows no further activity.
No specific error message is shown in the normal output, just the progress getting stuck and not advancing.
Expected Behavior
The docker compose build command should complete successfully and build the required Docker images without getting stuck or failing, allowing for a proper deployment of the relevant services.
Screenshots
[Not applicable as there is no specific visual indication other than the stuck progress display in the terminal, but can provide if needed in the future]
Environment (please complete the following information):
OS: macOS
Firecrawl Version: [Not applicable as not mentioned related to Firecrawl specifically]
Node.js Version: [Not applicable as not mentioned as relevant to this issue]
Docker Version (if applicable): [Version information not provided, but running in orbstack environment on macOS]
Database Type and Version: [Not applicable as not indicated to be related to a database issue in this context]
Logs
[No detailed logs available as the process just gets stuck without showing an error message in the console output. Will try to capture more detailed logs if possible and update.]
Configuration
[No specific configuration details provided as the issue seems to occur during the basic docker compose build process without any indication that a particular configuration setting is causing the problem.]
Additional Context
The issue occurs repeatedly in the orbstack environment on macOS. There have been no known modifications to the Docker setup other than the normal installation and running of commands in this environment, and no specific network or infrastructure changes that are known to be related to this problem.

[lukefan]

=> [api base 1/4] FROM docker.io/library/node:20-slim@sha256:aa15259095f820fc15499d36c2daaa17316b3146b3d2516bb418708cb3831f 1232.6s
=> => resolve docker.io/library/node:20-slim@sha256:aa15259095f820fc15499d36c2daaa17316b3146b3d2516bb418708cb3831f75 0.0s
=> => sha256:1a61ec8d59399330a764ab21145e711fdf476fc50ac8ccdb38dea1e3d9163796 1.93kB / 1.93kB 0.0s
=> => sha256:c86afbe3b01cdd1ffc9bf3d21ecd13202c9176bf24af9668cd0a58150b053440 6.56kB / 6.56kB 0.0s
=> => sha256:06191ad9adfe70fa8e5472c59bda366508230e9d5d3ceef4cec4b118f1ceac5b 0B / 40.73MB 1232.6s
=> => sha256:6b9df25993e6cf62eab414f662ed9359d0bfd661ea213e9bb6bcc2b12ca3df50 1.71MB / 1.71MB 5.8s
=> => sha256:2a08b3fc7ad730e33f66267de1ba2ac4d833183f5a1c95bb2e4f98d77e5e7307 447B / 447B 2.1s
=> => sha256:aa15259095f820fc15499d36c2daaa17316b3146b3d2516bb418708cb3831f75 6.49kB / 6.49kB 0.0s
=> [api go-base 1/3] FROM docker.io/library/golang:1.19@sha256:405b708c4612817e9966bff1469570eaed1ecf02a98055fb43bd6ca7b6401b3 0.0s
=> [api internal] load build context 0.0s
=> => transferring context: 22.68kB 0.0s
=> CACHED [api go-base 2/3] COPY sharedLibs/go-html-to-md /app/sharedLibs/go-html-to-md 0.0s
=> CACHED [api go-base 3/3] RUN cd /app/sharedLibs/go-html-to-md && go mod tidy && go build -o html-to-markdown.so -bu 0.0s

[nickscamara]

@tomkosm can you look into this pls?