Bodman implements minimum feature set of docker and podman. The original intuition is runing container under systemd more similar to a normal binary.

Inspired by bocker, podman and rkt.

It's only designed for running trusty image. If you find your docker image broken in bodman, just file a issue.

• ostree

You must pull you image manully before you use it (Maybe change in future).

bodman pull debian:testing
bodman run debian:testing /bin/bash

Current support run arguments:

NAME:
   bodman run -

USAGE:
   bodman run [command options] [arguments...]

OPTIONS:
   --help                               (default: false)
   --dns value                          (default: "8.8.8.8")
   --dns-option value, --dns-opt value
   --dns-search value
   --env value, -e value
   --hostname value, -h value
   --network value, --net value         (default: "host")
   --systemd-activation                 (default: false)
   --user value, -u value
   --volume value, -v value
   --workdir value, -w value

NOET: Port mapping is broken

• Fetch local image from docker/podman
• Maybe: OverlayFS and fuse-overlay

• Only support minimum feature, which removes a lot of complexities.
• Make it using like docker in most cases.

• PID Namespace: It only works when we fork a new process. That means we need a "supervisor" for the forked process. To simplify the design, just remove PID Namespace support because isolation is not the target.
• Isolation & Security: It's only designed for running trusty image. And removing features like cpu/memory limitation and capability control can eliminates most part of code.
• Build Image: It's only a complementary to current container ecosystem. You should still build your image using docker or podman.
• Daemon: Support running container as a daemon means we need a containerd. Like rkt, you can do it youself using systemd or just using podman or docker.