fix: include frontend with oss query-service

[davispuh]

Summary

#6696 updated ee/query-service/Dockerfile but didn't update pkg/query-service/Dockerfile

This causes query-service fail to start when using oss tagged images.
Workaround is to pass SIGNOZ_WEB_ENABLED=false env but it's not obvious because previously it just worked.

{
  "level": "FATAL",
  "timestamp": "2025-03-08T21:28:46.757Z",
  "caller": "query-service/main.go:99",
  "msg": "Failed to create signoz struct",
  "error": "cannot access web directory: stat /etc/signoz/web: no such file or directory",
  "stacktrace": "main.main\n\t/home/runner/work/signoz/signoz/pkg/query-service/main.go:99\nruntime.main\n\t/home/runner/go/pkg/mod/golang.org/[email protected]/src/runtime/proc.go:271"
}

Related Issues / PR's

• feat(ee): serve frontend pages with query-service #6696
• [Deprecation] Frontend Component #6762

Screenshots

NA

Affected Areas and Manually Tested Areas

---

Important

Fixes query-service startup failure by including frontend directory in pkg/query-service/Dockerfile.

• Dockerfile Update:
  • In pkg/query-service/Dockerfile, added COPY frontend/build/ /etc/signoz/web/ to include the frontend directory in the oss tagged images.
• Behavior:
  • Fixes startup failure of query-service due to missing frontend directory when using oss tagged images.
  • Previously required workaround of setting SIGNOZ_WEB_ENABLED=false is no longer necessary.

^{This description was created by for bcd62bc. It will automatically update as commits are pushed.}

[welcome]

Welcome to the SigNoz community! Thank you for your first pull request and making this project better. 🤗

[CLAassistant]

All committers have signed the CLA.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to bcd62bc in 1 minute and 0 seconds

More details

• Looked at 14 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. pkg/query-service/Dockerfile:27

• Draft comment:
  Ensure the target directory exists before copying. Docker often creates it, but explicitly creating the directory may improve clarity.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%

1. Docker's COPY command automatically creates target directories if they don't exist. 2. Creating directories explicitly is not a common practice in Dockerfiles unless there's a specific permission/ownership requirement. 3. The comment starts with "Ensure that..." which violates our rules. 4. The comment doesn't point out an actual problem - it's just a style suggestion that doesn't improve functionality.
   The comment might have merit if there were specific permission requirements for the web directory that needed to be set before copying.
   Even if directory permissions were a concern, they could be set after the COPY command. The current approach is standard Docker practice.
   Delete the comment as it starts with "Ensure that...", doesn't identify a real problem, and suggests an unnecessary change to standard Docker practices.

2. pkg/query-service/Dockerfile:26

• Draft comment:
  Document that copying the frontend build fixes the missing web directory issue (feat(ee): serve frontend pages with query-service #6696).
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. pkg/query-service/Dockerfile:27

• Draft comment:
  Consider adding a permission adjustment (chmod/chown) for /etc/signoz/web/ if query-service needs non-root access.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_TddtpkEENbEBXcjD

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[grandwizard28]

Hi @davispuh,
Thank you for the PR!

Apart from the changes mentioned here, we also need to change the corresponding github workflows for this to happen. We are in the process of revamping our CI and we plan to undertake this there itself.

[welcome]

Congrats on merging your first pull request!

We here at SigNoz are proud of you! 🥳