Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

docker-compose not working

未关闭
#17 1 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
docker, docker-compose

调研方向

Start by running docker compose up --build from the repository root and inspect docker-compose.yml and the OpenTelemetry collector's Dockerfile, which copies collector-config.yaml. Check the README.md for the documented setup and .env requirement. Done means the documented setup builds and starts without the dependency-cycle or missing-file errors.

由索引模型根据 Issue 内容生成。

描述

Hi,

I cloned the repo and launch the docker-compose command : docker compose up --build.
There was an error :

dependency cycle detected: api -> otel-collector -> api

I tried to modify the docker-compose.yml to remove the depends_on part from the otel-collector section.
Now there is an other error :

[+] Building 4.9s (16/16) FINISHED
 => [internal] load local bake definitions                             0.0s
 => => reading from stdin 2.34kB                                       0.0s
 => [ingest internal] load build definition from Dockerfile            0.1s
 => => transferring dockerfile: 453B                                   0.0s
 => [alerting internal] load build definition from Dockerfile          0.1s
 => => transferring dockerfile: 706B                                   0.0s
 => [api internal] load build definition from Dockerfile               0.1s
 => => transferring dockerfile: 722B                                   0.0s
 => [web internal] load build definition from Dockerfile               0.1s
 => => transferring dockerfile: 910B                                   0.0s
 => [otel-collector internal] load build definition from Dockerfile    0.1s
 => => transferring dockerfile: 211B                                   0.0s
 => [otel-collector internal] load metadata for docker.io/otel/opente  4.6s
 => [ingest internal] load metadata for docker.io/library/debian:book  3.1s
 => CANCELED [ingest internal] load metadata for docker.io/library/ru  4.7s
 => CANCELED [api internal] load metadata for docker.io/oven/bun:1.3.  4.7s
 => CANCELED [api internal] load metadata for docker.io/oven/bun:1.3.  4.7s
 => CANCELED [web internal] load metadata for docker.io/library/nginx  4.7s
 => [otel-collector internal] load .dockerignore                       0.0s
 => => transferring context: 213B                                      0.0s
 => [otel-collector internal] load build context                       0.0s
 => => transferring context: 2B                                        0.0s
 => CANCELED [otel-collector 1/2] FROM docker.io/otel/opentelemetry-c  0.0s
 => => resolve docker.io/otel/opentelemetry-collector-contrib:latest@  0.0s
 => ERROR [otel-collector 2/2] COPY collector-config.yaml /etc/otelco  0.0s
------
 [otel-collector 2/2] COPY collector-config.yaml /etc/otelcol/config.yaml:
------
> [+] up 0/5
 ⠙ Image maple-ingest         Building                                  4.9s
 ⠙ Image maple-alerting       Building                                  4.9s
 ⠙ Image maple-otel-collector Building                                  4.9s
 ⠙ Image maple-api            Building                                  4.9s
 ⠙ Image maple-web            Building                                  4.9s
Dockerfile:3

--------------------

   1 |     FROM otel/opentelemetry-collector-contrib:latest

   2 |

   3 | >>> COPY collector-config.yaml /etc/otelcol/config.yaml

   4 |

   5 |     EXPOSE 4317 4318 13133

--------------------

target otel-collector: failed to solve: failed to compute cache key: failed to calculate checksum of ref 3dkmvr904madb6y0ghi0jychg::pewwuqyot6f4vv7khevxw0682: "/collector-config.yaml": not found

Seems like files are missing.

Also I add to create an empty .env file in the root folder, else it wouldn't start docker-compose.
(This is not indicated in the README.md)

I did not push the tests further.

主要语言
TypeScript
星标
1.8k
派生
120
平均合并
8 小时 11 分钟
30 天内合并 PR
667

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

MapleTechLabs/maple 的其他 Issue

查看 MapleTechLabs/maple 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。