Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

4recommend
1warn against
Nov 3, 2025first mention
Sep 7, 2026latest mention
Nov 25 – Oct 26
Used forbuilding embedded linuxminimal linux image builds

Why people recommend it

“So much easier to keep track of everything and it's very easy to start with (unlike yocto). I recommend taking a look at buildroot.”

“by using Buildroot they got it down to acceptable boot times”

Show 2 more

“I'd just go with something like Buildroot”

“Which is not a case when you use OpenEmbedded/Yocto or Buildroot to build it.”

Caveats and dissent

“which I personally see little value in”

Often compared with

Who recommends it in their own words

All comments 7

“So much easier to keep track of everything and it's very easy to start with (unlike yocto). I recommend taking a look at buildroot.”

“by using Buildroot they got it down to acceptable boot times”

“I'd just go with something like Buildroot”

So if i have a docker container which needs a handful of packages, you would handle it how? I'm handling it by using a slim debian or ubuntu, then using apt to install these packages with necessary dependencies. For everything easy, like one basic binary, I use the most minimal image but as soon as it gets just a little bit annoying to set it up and keep it maintained, i start using apt and a nightly build of the ima

“which I personally see little value in”

“Which is not a case when you use OpenEmbedded/Yocto or Buildroot to build it.”

“he has it running with Buildroot already”

Threads where it came up

Also written as buildroot. Data: buildroot.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help