Skip to content

fix(embed): enable build rootfs disk growth - #3680

Open
selamanse wants to merge 1 commit into
e2b-dev:mainfrom
selamanse:fix/embed-build-rootfs-disk-growth
Open

selamanse wants to merge 1 commit into
e2b-dev:mainfrom
selamanse:fix/embed-build-rootfs-disk-growth

Conversation

@selamanse

Copy link
Copy Markdown

Summary

  • Allow BUILD_ENSURE_FREE_DISK_SPACE to set the fallback for the build disk-growth flag.
  • Enable the flag in the Embed Compose orchestrator, where LaunchDarkly is not configured.

This lets Embed builds grow their root filesystem after build steps so larger code tasks have enough space.

Validation

  • CI will run on the PR.

@cla-bot

cla-bot Bot commented Oct 13, 2026

Copy link
Copy Markdown

We require contributors to sign our Contributor License Agreement, and we don't have @selamanse on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check'

@selamanse

Copy link
Copy Markdown
Author

@cla-bot check

@cla-bot cla-bot Bot added the cla-signed label Oct 13, 2026
@cla-bot

cla-bot Bot commented Oct 13, 2026

Copy link
Copy Markdown

The cla-bot has been summoned, and re-checked this pull request!

@ThaRae

ThaRae commented Oct 21, 2026

Copy link
Copy Markdown

A data point for this one, from a self-hosted Embed (Compose) node. I ran an orchestrator built from ae948bd8759 (the commit behind the current Embed pin) with the same flags.go line. A template built with min_free_disk_mb=20480 gets an 813 MB rootfs without it, and a 22 GB rootfs with 21 GB free with it and BUILD_ENSURE_FREE_DISK_SPACE=true.

The Kubernetes shape needs the same setting in embed/kubernetes/statefulset.yaml. The sibling knobs (CREATE_MEMORY_REFUSAL, PAUSE_ADMISSION_DISK_HEADROOM_MIB) also come with an embed/tests/*.bats check for both shapes. I have that version on a branch, with docs, if it helps: ThaRae@67e65d1 (branch embed-build-ensure-free-disk-space-env)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants