Skip to content

Commit 4affb62

Browse files
Julian Stecklinablitz
Julian Stecklina
authored andcommitted
doc: add a section about building with glibc
Signed-off-by: Julian Stecklina <[email protected]>
1 parent 9698485 commit 4affb62

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/getting-started.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -251,6 +251,25 @@ arguments is available via:
251251
tools/devtool --help
252252
```
253253

254+
### Alternative: Building Firecracker using glibc
255+
256+
The toolchain that Firecracker is tested against and that is recommended for
257+
building production releases is the one that is automatically used by building
258+
using `devtool`. In this configuration, Firecracker is currently built as a
259+
static binary linked against the [musl](https://www.musl-libc.org/) libc
260+
implementation.
261+
262+
Firecracker also builds using [glibc](https://www.gnu.org/software/libc/)
263+
toolchains, such as the default Rust toolchains provided in certain Linux
264+
distributions:
265+
266+
```bash
267+
cargo build --target x86_64-unknown-linux-gnu
268+
```
269+
270+
That being said, Firecracker binaries built without `devtool` are always
271+
considered experimental and should not be used in production.
272+
254273
## Running the Integration Test Suite
255274

256275
You can also use our development tool to run the integration test suite:

0 commit comments

Comments
 (0)