withastro/astro

Transport invoke timed out after 60000ms / Docker and WSL issues

Closed

#15,101 opened on Jan 3, 2026

View on GitHubContributor guide
 (9 comments) (4 reactions) (0 assignees)TypeScript (3,742 forks)batch import
help wantedin reviewtriage: skipped

Repository metrics

Stars
 (61,991 stars)
PR merge metrics
 (PR metrics pending)

Description

Astro Info

Astro                    v5.7.13
Node                     v24.12.0
System                   Windows (x64)
Package Manager          pnpm
Output                   server
Adapter                  @astrojs/node
Integrations             @astrojs/react

Even latest version of Astro has this issue.

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

This started about 3-4 days ago and I've been troubleshooting it for days with no clear errors. Only happens with running astro in dev mode.

[ERROR] transport invoke timed out after 60000ms (data: {"type":"custom","event":"vite:invoke","data":{"name":"fetchModule"...}})

Reproduction

Having timeout/slow loads issues :

pnpm dev in WSL2 terminal, project on Windows filesystem

and

pnpm dev in WSL2 terminal, project on WSL filesystem (loads but has hydration / css / html issues)

and

pnpm dev in Docker (Both WSL and Windows filesystem)

What's the expected result?

Normally pnpm dev would work in docker. Also I would expect pnpm dev in WSL2 terminal, project on WSL filesystem to work as well.

Link to Minimal Reproducible Example

N/A

Participation

  • I am willing to submit a pull request for this issue.

Contributor guide

Research direction
Examine the transport invoke timeout in Astro's dev server. Look into Vite's file system watching and how it interacts with Docker/WSL. Check if the issue is related to filesystem polling or network bindings.
Tech stack
typescriptnodejsdocker
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.jsDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40