Set up the proxy on a random port that's queryable from the control API

Metadata

Project: fetch-service
Number: #354
Type: issue
State: open
Author: lengau
Labels: —
Created: 2025-03-06 11:54 PM UTC
Updated: 2025-08-15 03:15 PM UTC
Closed: —

Current evaluation

Requests a runtime-selected proxy port exposed through the control API; it remains open and unlabeled, and current code still uses a fixed default proxy port.

Suggested action: needs triage

Reason: The gap is confirmed in the code: cmd/fetch/main.go defines --proxy-port with a default of 9988, proxy.Start binds that fixed address, and ServiceStatus has no proxy-port field. Although the maintainer-authored request has a clear motivation and reproducible limitation, it has no labels, comments, or assignee, and the CLI/API shape and port-discovery timing remain unspecified.

Evaluated by: mr-cal-bot

Impact: 60 Quick Win: 18 Complexity: 55 Confidence: 88 Actionability: 68

Issue body

### What needs to get done If the user doesn't pass a proxy port (or perhaps if the user explicitly passes `--random-proxy-port` or similar), set up the proxy on a random port. The control API must have a way to query the proxy port. ### Why it needs to get done Combined with https://github.com/canonical/fetch-service/issues/353 this removes the static nature of the ports, letting us control on a unix socket and proxy over any unused port. This makes it possible to run multiple crafts with `--enable-fetch-service` simultaneously (which is good because fetch service enabled builds are by their nature slow)

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-02 08:41 PM UTC	stealth/space-bunny-alpha	Impact: 60 Quick Win: 18 Complexity: 55 Confidence: 88 Actionability: 68	needs triage	Requests a runtime-selected proxy port exposed through the control API; it remains open and unlabeled, and current code still uses a fixed default proxy port.
2026-10-02 08:40 PM UTC	stealth/space-bunny-alpha	Impact: 64 Quick Win: 21 Complexity: 58 Confidence: 92 Actionability: 78	needs triage	Add runtime-selected proxy ports exposed through the control API to support concurrent fetch-enabled builds; the feature remains open and untriaged while the code still defaults to static port 9988.
2026-10-02 08:40 PM UTC	stealth/space-bunny-alpha	Impact: 68 Quick Win: 24 Complexity: 48 Confidence: 90 Actionability: 68	keep open	Runtime-selected proxy ports and status exposure remain unimplemented; the default is still 9988, limiting concurrent fetch-enabled builds and the Unix-socket work tracked in #353.
2026-09-24 09:27 PM UTC	stealth/space-bunny-alpha	Impact: 57 Quick Win: 24 Complexity: 45 Confidence: 88 Actionability: 76	needs triage	Select an available proxy port at runtime and expose it through the control API to support Unix-socket control and concurrent fetch-enabled builds; currently untriaged.
2026-09-09 04:26 PM UTC	qwen/qwen3.6-35b-a3b	Impact: 60 Quick Win: 30 Staleness: 75 Complexity: 50 Confidence: 60 Support Request: 10	needs triage	Feature request to allow proxy on random port with control API query endpoint. Unlabelled, no comments, inactive for 390 days.

Update history

Date	Change
2025-08-15 03:15 PM UTC	created

Related work

Related To: canonical/fetch-service#353 (confidence 100%)
Explicitly linked companion issue; Unix-socket control and runtime proxy-port selection are intended to remove the remaining static-port constraints for concurrent builds.

Related issues

No related issues found above the similarity threshold.