Change sandboxes local hostname to e2b

[dobrac]

Change the sandboxes hostname from e2b.local to just e2b. This should prevent conflicts with mDNS resolver.

---

[!NOTE] Changes the sandbox hostname from e2b.local to e2b in packages/orchestrator/internal/template/build/core/rootfs/rootfs.go, updating the generated /etc/hosts.

• Rootfs template:
  • Update default hostname to e2b (from e2b.local) in packages/orchestrator/internal/template/build/core/rootfs/rootfs.go, which updates the generated /etc/hosts entry.

^{Written by Cursor Bugbot for commit 89bd4d377b1cd6c221726210d0957c1c1c90e399. This will update automatically on new commits. Configure here.}

[tomassrnka]

✅ e2b (Recommended)

Follows systemd's official recommendation (short name without dots) Avoids the hostnamectl bug that strips dots from FQDNs Maximum compatibility across all Linux distributions You can still get FQDN resolution by adding an entry to /etc/hosts or proper DNS

❌ e2b.local (Avoid)

Violates RFC 6762 - .local is reserved for mDNS only Will break on Apple devices (macOS/iOS) which automatically use mDNS for .local Causes Avahi to auto-rename your host to e2b-2, e2b-3 after network changes Mixed unicast DNS + mDNS creates unpredictable resolution failures

❌ e2b.localhost (Wrong use case)

RFC 6761 reserves .localhost to always resolve to 127.0.0.1/::1 Perfect for local web development, but useless for anything involving network communication Can't be used for services that need to be accessible from other machines

[sitole]

Shouldn’t we also change events domain in envd?

[dobrac]

Shouldn’t we also change events domain in envd?

do you think having events.e2b is a good idea there?

[dobrac]

We'll add a new domain for this case. Let's change it directly to that domain once we have it set.