fix(docker): make runtime dir creation non-fatal in entrypoint#288
Merged
viettranx merged 1 commit intonextlevelbuilder:mainfrom Mar 20, 2026
Merged
Conversation
On first start with a fresh Docker volume, mkdir for .runtime subdirectories can fail due to a volume initialisation race condition, causing the container to restart loop. The directories are only needed for agent-installed packages (pip/npm), so the failure is non-fatal.
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.
Summary
mkdir -pcalls for.runtimesubdirectories non-fatal (|| true) indocker-entrypoint.shTest plan
make env-dockerwith fresh volume — no restart loop, gateway healthy on first attemptmake env-down-dockerworks cleanly