Handle internal sandbox events from sandboxes in orchestrator

[0div]

Description

Setup networking in sandbox for events endpoint and handle sandbox events at the orchestrator level.

• implement sandbox event proxy server to capture http requests to events endpoints inside sandboxes
• create handler abstraction
• map sandboxIPs-to-sandboxIDs
• introduce consts.go file in orchestrator and add the sandbox event IP and port

Test

[infra]
$ make build-and-upload/envd # with mmds changes 
$ make build-and-upload/template-manager # with changes from https://github.com/e2b-dev/infra/pull/1107
$ make build-and-upload/orchestrator # with changes from this PR 
$ make plan
$ make apply 

[E2B/template/base]
$ e2b template build

[Sandbox]
user@e2b:~$ cat /etc/hosts
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::  ip6-localnet
ff00::  ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 e2b.local
203.0.113.0 events.e2b.dev 

$ e2b sbx sp base
user@e2b:~$ curl -X POST http://events.e2b.dev/proc -d '{ "pid": 123 }'

{"event_ack": true }

[linear]

E2B-2962 Handle sandbox events at the orchestrator level

[0div]

@sitole @dobrac , i made the /etc/hosts update dynamically with new MMDS event address field. I tried a few IPs from local link range (169.254.0.1, 169.254.0.7) but it doesn't work, so i kept it to TEST-NET-3 IP for now

[0div]

@sitole once #1107 is merged, i can add integration test here

[cursor]

Bug: IP Extraction Fails on IPv6 Addresses

The IP address extraction from r.RemoteAddr using strings.Split(addr, ":")[0] is unreliable. It incorrectly parses IPv6 addresses (e.g., [::1]:port results in [::1 or [) and is fragile, as RemoteAddr's format isn't guaranteed to be ip:port. This can lead to an incorrect sandboxIP.

packages/orchestrator/internal/events/sandbox_events_handlers.go#L30-L32

infra/packages/orchestrator/internal/events/sandbox_events_handlers.go

Lines 30 to 32 in 4c96bff

	func (h *DefaultSandboxEventHandler) HandlerFunc(w http.ResponseWriter, r *http.Request) {
	addr := r.RemoteAddr
	sandboxIP := strings.Split(addr, ":")[0]

 

---

Bug: Redis Client Nil Checks Inconsistent

Several sandboxEventStore methods, such as GetSandboxID and DelSandboxIP, don't check if redisClient is nil before use, unlike SetSandboxIP. This inconsistency could lead to nil pointer panics if the client isn't initialized.

packages/orchestrator/internal/events/sandbox_events_store.go#L54-L67

infra/packages/orchestrator/internal/events/sandbox_events_store.go

Lines 54 to 67 in 4c96bff

	func (c *sandboxEventStore) SetSandboxIP(ctx context.Context, sandboxID string, sandboxIP string) error {
	if c.redisClient == nil {
	return fmt.Errorf("redisClient is nil")
	}
	return c.redisClient.Set(ctx, IPPrefix+sandboxIP, sandboxID, cacheTL).Err()
	}
	func (c *sandboxEventStore) GetSandboxID(ctx context.Context, sandboxIP string) (string, error) {
	return c.redisClient.Get(ctx, IPPrefix+sandboxIP).Result()
	}
	func (c *sandboxEventStore) DelSandboxIP(ctx context.Context, sandboxIP string) error {
	return c.redisClient.Del(ctx, IPPrefix+sandboxIP).Err()
	}

 

---

[sitole]

#1107 is merged so we can rebase this one.
Probably you can build on top of #1233 that adds gin http server for hyperloop server.