cloudflare / cloudflare/containers
Container not ready on cold start - "not listening on TCP address" error
- Dominant language
- TypeScript
- Stars
- 270
- Forks
- 42
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 4
Description
Hi, I have a docker container of a Laravel application built with frankenphp and every time I send a request when the container is in "Ready" state it fails with the following error:
Container error: The container is not listening in the TCP address 10.0.0.1:8080
After some seconds (like 2-3 seconds) I do the exact same request and it returns correct data...
Any idea on how to fix this? Have seen the docs but can't figure it out.
Contributor guide
Research direction
Reproduce the cold-start request against the Dockerized Laravel/FrankenPHP container and inspect startup logs alongside the readiness state. Done means a request sent immediately after the platform reports Ready succeeds without the TCP-listening error, rather than only succeeding after the reported 2–3 second delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, laravel
- Domain
- backend, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100