Got Errors on Running Docker Compose Up
Opened this issue · 2 comments
Describe the bug
I got errors when running docker-compose -f caMicroscope.yml up
on this project (master branch). I use this command to capture the log docker-compose -f caMicroscope.yml up > output.txt 2> error.txt
.
Can you please guide me on how to solve this? Thank you in advance!
Here are the logs
error.txt
output.txt
To Reproduce
Steps to reproduce the behavior:
- Clone Distro repository
https://github.com/camicroscope/Distro.git
- Run docker compose up
docker-compose -f caMicroscope.yml up
- See error
Expected behavior
The system runs smoothly and we can access it on http://localhost:4010
Screenshots
You can find detailed logs on the files I attached
Desktop (please complete the following information):
- OS: Windows 11
- Docker Version
$ docker version
Client:
Cloud integration: v1.0.33
Version: 24.0.2
API version: 1.43
Go version: go1.20.4
Git commit: cb74dfc
Built: Thu May 25 21:53:15 2023
OS/Arch: windows/amd64
Context: default
Server: Docker Desktop 4.20.1 (110738)
Engine:
Version: 24.0.2
API version: 1.43 (minimum version 1.12)
Go version: go1.20.4
Git commit: 659604f
Built: Thu May 25 21:52:17 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.21
GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc:
Version: 1.1.7
GitCommit: v1.1.7-0-g860f061
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Additional context
This is my first time running this repository. I also tried to use docker compose -f caMicroscope.yml up
(without hyphen -
), but I still get the same error
docker-compose -f develop.yml build loader --no-cache
docker-compose -f caMicroscope.yml build
docker-compose -f caMicroscope.yml up
try this
Hi @barchakuz , thank you so much for helping me!
I successfully run docker-compose -f develop.yml build loader --no-cache
and docker-compose -f caMicroscope.yml build
. But, I still got errors when running docker-compose -f caMicroscope.yml up
, the same errors as previously. I also tried to remove all docker images on my local, but I still got the same errors as well