Environment: Windows 11, Docker Desktop (context desktop-linux, confirmed healthy), WSL2 docker-desktop distro confirmed Running.
Command: genlayer up --headless
Result: Process spawns docker compose -p genlayer up -d and stays alive but idle — no containers created, no genlayer project appears in docker compose ls, no network connection associated with the process, port 127.0.0.1:4000 never opens. Output never advances past Checking CLI version....
Ruled out before filing: npm registry connectivity (confirmed working), GitHub API rate limiting (x-ratelimit-remaining: 58 at time of test), stale CLI lock/PID files (none found under %USERPROFILE%\.genlayer), orphaned child processes from a prior killed attempt (none found), Docker context/WSL2 health (confirmed healthy on both).
Possibly related to a JSON-RPC startup issue also seen with the local Studio stack, filed separately — both may share a root cause in local image/version resolution, though this isn’t confirmed.
Happy to share full logs on request.
Environment: Windows 11, Docker Desktop (context
desktop-linux, confirmed healthy), WSL2docker-desktopdistro confirmedRunning.Command:
genlayer up --headlessResult: Process spawns
docker compose -p genlayer up -dand stays alive but idle — no containers created, nogenlayerproject appears indocker compose ls, no network connection associated with the process, port127.0.0.1:4000never opens. Output never advances pastChecking CLI version....Ruled out before filing: npm registry connectivity (confirmed working), GitHub API rate limiting (
x-ratelimit-remaining: 58at time of test), stale CLI lock/PID files (none found under%USERPROFILE%\.genlayer), orphaned child processes from a prior killed attempt (none found), Docker context/WSL2 health (confirmed healthy on both).Possibly related to a JSON-RPC startup issue also seen with the local Studio stack, filed separately — both may share a root cause in local image/version resolution, though this isn’t confirmed.
Happy to share full logs on request.