docs(v1.5): add fly.io service startup timeout workaround#310
Merged
docs(v1.5): add fly.io service startup timeout workaround#310
Conversation
Nonnyjoe
approved these changes
Mar 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Cartesi rollups node v1.5 go-supervisor has a hard-coded 5-second startup timeout per service. On Fly.io,
inspect-server(and occasionallyserver-manager) take longer than 5 seconds to become ready, causing the node to restart immediately after launch.Change
Added a Known issue caution block to the v1.5 Hosting on fly.io section that:
Dockerfile.fly(hosted at Mugen-Builders/cartesi-flyio-workaround) that replaces the go-supervisor with nitro + nginx, which have no startup timeoutDockerfile.flyinstead of tagging the default imageRelated
A root-cause fix (making the timeout configurable via
CARTESI_SERVICE_READY_TIMEOUT) is proposed in cartesi/rollups-node#750. Once that is merged and released, this workaround section can be replaced with a simple env-var note.