BuildKit TCP service behind HTTP reverse proxy

Open
#1,464 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, nginx
Domain
networking

Research direction

Start with the BuildKit daemon's TCP service and the NGINX TCP-forwarding setup described in the issue. Investigate the difference between TCP forwarding and HTTP reverse proxying, then establish whether HTTP proxy traffic can be supported and how that behavior should be verified.

Written by the indexing model from the issue text.

Description

kind/question

Is it possible for the BuildKit daemon deployed as a TCP service to receive traffic behind an HTTP reserve proxy? I've been able to access the daemon behind NGINX configured to forward TCP traffic but not with HTTP proxying.

Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.