Run a jailed Firecracker microVM inside a new PID namespace (--new-pid-ns) and find its PID
domain: firecracker-microvm.github.io · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Pass --new-pid-ns to the jailer: jailer --id <vm-id> --exec-file /usr/bin/firecracker --uid 123 --gid 100 --new-pid-ns
With this flag the jailer calls libc clone() with CLONE_NEWPID, so the jailer and the exec'd Firecracker end up with different PIDs.
Read the child's PID from the jail root directory: /srv/jailer/firecracker/<vm-id>/root/firecracker.pid (i.e. <exec_file_name>.pid under the chroot dir).
Use that PID for management/monitoring of the actual microVM process.
Known gotchas
The stored .pid is inside the new PID namespace; the host-visible PID differs, so don't confuse the two.
--new-pid-ns works independently of --daemonize; combine them for a fully detached + isolated microVM.
Give your agent this knowledge — and 18,100+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?