Skip to content

[Backport release-2.4] render: Have the context function listen on a TCP port#173

Merged
adamwg merged 1 commit into
release-2.4from
backport-163-to-release-2.4
Jun 30, 2026
Merged

[Backport release-2.4] render: Have the context function listen on a TCP port#173
adamwg merged 1 commit into
release-2.4from
backport-163-to-release-2.4

Conversation

@github-actions

Copy link
Copy Markdown

Description

Backport of #163 to release-2.4.

Previously, the context function (which injects and extracts function pipeline
context when rendering) listened on a unix socket. This didn't work in
environments where containers don't share a kernel with the CLI (e.g., macOS
with Docker Desktop), causing render to time out in such environments.

Update the context function to listen on a TCP port. We already handle functions
listening on TCP on the host, since this is how the "development" function
runtime works. Note that we have to listen on 0.0.0.0 (not localhost/127.0.0.1)
to ensure we're reachable from Docker.

Fixes #161

Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
(cherry picked from commit e80ffa7)
@github-actions github-actions Bot requested review from a team, jcogilvie and tampakrap as code owners June 30, 2026 17:21
@github-actions github-actions Bot requested review from adamwg and removed request for a team June 30, 2026 17:21
@adamwg adamwg merged commit 1e9511e into release-2.4 Jun 30, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant