mirror of
https://github.com/containers/youki
synced 2026-04-24 09:21:14 +02:00
f07d0fdf88
Matches runc's behavior where a non-leave-running checkpoint fully removes the container from runtime state. Previously youki only set the status to Stopped, leaving the container accessible via `state <id>`. Also update lifecycle checkpoint tests to verify process liveness and container state deletion based on the --leave-running flag. Signed-off-by: nayuta723 <nayuta723@gmail.com> |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| README.md | ||
libcontainer
Building with musl
In order to build with musl you must first remove the libseccomp dependency as it will reference shared libraries (libseccomp) which cannot be built with musl.
Do this by using adding flags to Cargo. Use the --no-default-features flag followed by -F and whatever features you intend to build with such as v2 as defined in Cargo.toml under features section.
Next you will also need the +nightly flags when building with rustup and cargo.
# Add rustup +nightly musl to toolchain
rustup +nightly target add $(uname -m)-unknown-linux-musl
# Build rustup +nightly stdlib with musl
rustup +nightly toolchain install nightly-$(uname -m)-unknown-linux-musl
# Build musl standard library
cargo +nightly build -Zbuild-std --target $(uname -m)-unknown-linux-musl --no-default-features -F v2
cargo +nightly build --target $(uname -m)-unknown-linux-musl --no-default-features -F v2