#process #init #container #cli #pid1

app pid1-exe

pid1 handling library for proper signal and zombie reaping of the PID1 process

4 releases

0.1.3 Nov 14, 2023
0.1.2 Oct 6, 2023
0.1.1 Oct 4, 2023
0.1.0 Oct 3, 2023

#1007 in Command line utilities

MIT license

254 lines


Crates.io Crates.io Rust

pid1 handling library for proper signal and zombie reaping of the PID1 process.

This repository consists of two packages:

  • pid1 crate: Library meant to be used by your Rust applications.
  • pid1-exe crate: Binary which internally uses pid1 crate for container deployments. The binary name is pid1.

pid1 Library Usage

This library is used to simplify Rust deployment in a containerized environment. Instead of using binaries like Haskell's pid1 or tini in your container, you can use this crate directly.

You must ensure that the launch method is the first statement in your main function:

use std::time::Duration;
use pid1::Pid1Settings;

fn main() {
        .expect("Launch failed");
    println!("Hello world");
    // Rest of the logic...

You can also see various example usages here. This function is meant only for Unix systems and the above code is a no-op in Windows.

Using pid1 binary

You can download the pid1 binary that is part of the releases and use it in your container directly. Example:

FROM alpine:3.14.2

ADD https://github.com/fpco/pid1-rs/releases/download/v0.1.0/pid1-x86_64-unknown-linux-musl /usr/bin/pid1

RUN chmod +x /usr/bin/pid1

ENTRYPOINT [ "pid1" ]

Various options supported by the binary:

❯ pid1 --help

  <COMMAND>  Process to run
  [ARGS]...  Arguments to the process

  -w, --workdir <DIR>        Specify working direcory
  -t, --timeout <TIMEOUT>    Timeout (in seconds) to wait for child proess to exit [default: 2]
  -v, --verbose              Turn on verbose output
  -e, --env <ENV>            Override environment variables. Can specify multiple times
  -u, --user-id <USER_ID>    Run command with user ID
  -g, --group-id <GROUP_ID>  Run command with group ID
  -h, --help                 Print help


The testing steps are documented in Development.md. We only have some part of it integrated in CI.


~71K SLoC