containers: Add container and test Containers interceptOutboundHttp

[gabivlj]

Adds configuration backed by a experimental flag to allow direct communication to Workers from Containers.

There is an example in the integration test, how this feature works is that you can now define a HTTP IP:port mapping to a WorkerEntrypoint. All requests done in the container to that endpoint end up spawning a Worker to serve the request.

To enable this feature, use the experimental flag experimental in the configuration.

export class TestService extends WorkerEntrypoint {
  async fetch(req: Request) {
    return new Response("hello from worker");
  }
}

...

await this.container.interceptOutboundHttp(
  "11.0.0.1:80",
  this.ctx.exports.TestService({ props: {} }),
);


... inside container

console.log(await (await fetch('11.0.0.1:80')).text()); // hello from worker										);

You can also use the very convenient:

this.ctx.container.interceptAllOutboundHttp(this.ctx.exports.TestService({ props: {} }))

It won't work with HTTPS yet, of course. Stay tuned for that.

Note: This feature is experimental and subject to change.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: Experimental feature for now that we are testing. Once preparation for GA begins, we will add public cloudflare-docs

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

🦋 Changeset detected

Latest commit: ee032d7

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@12649

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@12649

miniflare

npm i https://pkg.pr.new/miniflare@12649

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@12649

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@12649

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@12649

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@12649

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@12649

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@12649

wrangler

npm i https://pkg.pr.new/wrangler@12649

commit: 51c3b36

[claude]

Claude finished @gabivlj's task —— View job

---

Changeset Review

✅ All changesets look good

The changeset in .changeset/empty-radios-happen.md follows all the guidelines:

• Version Type: Correctly marked as minor for a new experimental feature
• Changelog Quality: Clear description with explanation of the feature and explicit note about experimental status requiring a flag
• Markdown Headers: No h1/h2/h3 headers present
• Experimental Feature Note: ✅ Includes note on how users can opt in ("requires enabling the 'experimental' flag")

---

This is a polar bear. Very close to the camera. Doing a heckin good sniff. Magnificent snoot. 14/10 would definitely not try to pet.

[github-actions]

⚠️ Issues found

File: .changeset/empty-radios-happen.md

Issue: Insufficient opt-in instructions for experimental feature

The changeset correctly uses minor for an experimental feature and mentions that a compatibility flag is required, but the description does not specify which compatibility flag users need to add. Per the README guidelines, experimental features should explicitly call out how users can opt in.

The current description says:

"This feature is experimental and requires adding the 'experimental' compatibility flag to your Wrangler configuration."

This is too vague. The changeset should name the specific compatibility flag (e.g. "experimental_containers_intercept_outbound_http" or whatever the actual flag name is) and ideally include a brief wrangler.json example showing how to enable it.

Suggested improvement:

Add experimental support for containers to workers communication with interceptOutboundHttp

This feature is experimental. To opt in, add the `<specific-flag-name>` compatibility flag to your `wrangler.json`:

```json
{
  "compatibility_flags": ["<specific-flag-name>"]
}

Please update the changeset to include the specific flag name and a configuration example.

<!-- Sticky Pull Request Commentchangeset-review -->

[emily-shen]

and i've manually tested this on macOS and it works great 🎉

Changes in owned files since last approval

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/cloudchamber
• ✅ @cloudflare/wrangler

Show detailed file reviewers

Changes in owned files since last approval