Skip to content

ENAMETOOLONG error with native runtime #4173

Description

@Tropicalista

Quick summary

When I enable the new "NATIVE" runtime, I got this error:

[2026-07-10T15:12:51.873Z][info][main] [CLI - f7cd70b3-004e-4a6b-afdc-cf90b5889dc9] Starting WordPress server…
[2026-07-10T15:14:31.601Z][erro][main] Error occurred in handler for 'startServer': CliCommandError: [Last error message] Failed to start WordPress server: spawn ENAMETOOLONG
  [Base message] Failed to start site
  [Exit code] 1
[2026-07-10T15:14:31.621Z][info][main] Stopping server with ID f7cd70b3-004e-4a6b-afdc-cf90b5889dc9

The old sandbox option is working fine.

Steps to reproduce

  1. Start site

What you expected to happen

Start the site

What actually happened

I got an error ENAMETOOLONG

Impact

One

Available workarounds?

No but the app is still usable

Platform

Windows

Logs or notes

[2026-07-10T15:12:51.873Z][info][main] [CLI - f7cd70b3-004e-4a6b-afdc-cf90b5889dc9] Starting WordPress server…
[2026-07-10T15:14:31.601Z][erro][main] Error occurred in handler for 'startServer': CliCommandError: [Last error message] Failed to start WordPress server: spawn ENAMETOOLONG
[Base message] Failed to start site
[Exit code] 1
[2026-07-10T15:14:31.621Z][info][main] Stopping server with ID f7cd70b3-004e-4a6b-afdc-cf90b5889dc9

Metadata

Metadata

Assignees

Type

Fields

No fields configured for Bug.

Projects

Status
Triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions