.. | ||
pkg | ||
.gitignore | ||
.travis.yml | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
Makefile | ||
README.md |
RootlessKit: the gate to the rootless world
rootlesskit
is a kind of Linux-native "fake root" utility, made for mainly running Docker and Kubernetes as an unprivileged user.
rootlesskit
does an equivalent of unshare(1)
and newuidmap(1)
/newgidmap(1)
in a single command, for creating unprivileged user_namespaces(7)
and mount_namespaces(7)
with subuid(5)
and subgid(5)
.
rootlesskit
also supports network namespace isolation and userspace NAT using "slirp".
Kernel NAT using SUID-enabled lxc-user-nic(1)
is also on the plan.
Projects using RootlessKit
- Usernetes: Docker & Kubernetes, installable under a non-root user's
$HOME
. - BuildKit: Next-generation
docker build
backend
Setup
$ go get github.com/rootless-containers/rootlesskit/cmd/rootlesskit
$ go get github.com/rootless-containers/rootlesskit/cmd/rootlessctl
Requirements:
- Some distros such as Debian (excluding Ubuntu) and Arch Linux require
sudo sh -c "echo 1 > /proc/sys/kernel/unprivileged_userns_clone"
. newuidmap
andnewgidmap
need to be installed on the host. These commands are provided by theuidmap
package on most distros./etc/subuid
and/etc/subgid
should contain >= 65536 sub-IDs. e.g.penguin:231072:65536
.
$ id -u
1001
$ whoami
penguin
$ grep ^$(whoami): /etc/subuid
penguin:231072:65536
$ grep ^$(whoami): /etc/subgid
penguin:231072:65536
Usage
Inside rootlesskit
, your UID is mapped to 0 but it is not the real root:
$ rootlesskit bash
rootlesskit$ id
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
rootlesskit$ ls -l /etc/shadow
-rw-r----- 1 nobody nogroup 1050 Aug 21 19:02 /etc/shadow
rootlesskit$ $ cat /etc/shadow
cat: /etc/shadow: Permission denied
Environment variables are kept untouched:
$ rootlesskit bash
rootlesskit$ echo $USER
penguin
rootlesskit$ echo $HOME
/home/penguin
rootlesskit$ echo $XDG_RUNTIME_DIR
/run/user/1001
Filesystems can be isolated from the host with --copy-up
:
$ rootlesskit --copy-up=/etc bash
rootlesskit$ rm /etc/resolv.conf
rootlesskit$ vi /etc/resolv.conf
You can even create network namespaces with Slirp:
$ rootlesskit --copy-up=/etc --copy-up=/run --net=slirp4netns bash
rootlesskit$ ip netns add foo
...
Proc filesystem view:
$ rootlesskit bash
rootlesskit$ cat /proc/self/uid_map
0 1001 1
1 231072 65536
rootlesskit$ cat /proc/self/gid_map
0 1001 1
1 231072 65536
rootlesskit$ cat /proc/self/setgroups
allow
Full CLI options:
$ rootlesskit --help
NAME:
rootlesskit - the gate to the rootless world
USAGE:
rootlesskit [global options] command [command options] [arguments...]
VERSION:
0.3.0-alpha.0
COMMANDS:
help, h Shows a list of commands or help for one command
GLOBAL OPTIONS:
--debug debug mode
--state-dir value state directory
--net value network driver [host, slirp4netns, vpnkit, vdeplug_slirp] (default: "host")
--slirp4netns-binary value path of slirp4netns binary for --net=slirp4netns (default: "slirp4netns")
--vpnkit-binary value path of VPNKit binary for --net=vpnkit (default: "vpnkit")
--mtu value MTU for non-host network (default: 65520 for slirp4netns, 1500 for others) (default: 0)
--cidr value CIDR for slirp4netns network (default: 10.0.2.0/24, requires slirp4netns v0.3.0+ for custom CIDR)
--disable-host-loopback prohibit connecting to 127.0.0.1:* on the host namespace
--copy-up value mount a filesystem and copy-up the contents. e.g. "--copy-up=/etc" (typically required for non-host network)
--copy-up-mode value copy-up mode [tmpfs+symlink] (default: "tmpfs+symlink")
--port-driver value port driver for non-host network. [none, socat] (default: "none")
--help, -h show help
--version, -v print the version
Building from source
rootlesskit
and rootlessctl
can be built from source using:
make
State directory
The following files will be created in the --state-dir
directory:
lock
: lock filechild_pid
: decimal PID text that can be used fornsenter(1)
.api.sock
: REST API socket forrootlessctl
. See Port forwarding section.
Undocumented files are subject to change.
Environment variables
The following environment variables will be set for the child process:
ROOTLESSKIT_STATE_DIR
(since v0.3.0): absolute path to the state dir
Undocumented environment variables are subject to change.
Slirp
Remarks:
- Specifying
--copy-up=/etc
is highly recommended unless/etc/resolv.conf
is statically configured. Otherwise/etc/resolv.conf
will be invalidated when it is recreated on the host, typically by NetworkManager or systemd-resolved.
Currently there are three slirp implementations supported by rootlesskit:
--net=slirp4netns
, using slirp4netns (recommended)--net=vpnkit
, using VPNKit--net=vdeplug_slirp
, using vdeplug_slirp
Usage:
$ rootlesskit --state-dir=/run/user/1001/rootlesskit/foo --net=slirp4netns --copy-up=/etc bash
rootlesskit$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 42:b6:8d:e4:02:c4 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.100/24 scope global tap0
valid_lft forever preferred_lft forever
inet6 fe80::40b6:8dff:fee4:2c4/64 scope link
valid_lft forever preferred_lft forever
rootlesskit$ ip r
default via 10.0.2.2 dev tap0
10.0.2.0/24 dev tap0 proto kernel scope link src 10.0.2.100
rootlesskit$ cat /etc/resolv.conf
nameserver 10.0.2.3
rootlesskit$ curl https://www.google.com
<!doctype html><html ...>...</html>
Default network configuration for --net=slirp4netns
and --net=vdeplug_slirp
:
- IP: 10.0.2.100/24
- Gateway: 10.0.2.2
- DNS: 10.0.2.3
- Host: 10.0.2.2, 10.0.2.3
Default network configuration for --net=vpnkit
:
- IP: 192.168.65.3/24
- Gateway: 192.168.65.1
- DNS: 192.168.65.1
- Host: 192.168.65.2
--net=slirp4netns
supports specifying custom CIDR, e.g. --cidr=10.0.3.0/24
(requires slirp4netns v0.3.0+)
It is highly recommended to disable host loopback address by specyfing --disable-host-loopback
.
Port forwarding
rootlessctl
can be used for exposing the ports in the network namespace to the host network namespace.
You also need to launch rootlesskit
with --port-driver=(socat|slirp4netns|builtin)
. builtin
is the fastest but currently experimental.
For example, to expose 80 in the child as 8080 in the parent:
$ rootlesskit --state-dir=/run/user/1001/rootlesskit/foo --net=slirp4netns --copy-up=/etc --port-driver=socat bash
rootlesskit$ rootlessctl --socket=/run/user/1001/rootlesskit/foo/api.sock add-ports 0.0.0.0:8080:80/tcp
1
rootlesskit$ rootlessctl --socket=/run/user/1001/rootlesskit/foo/api.sock list-ports
ID PROTO PARENTIP PARENTPORT CHILDPORT
1 tcp 0.0.0.0 8080 80
rootlesskit$ rootlessctl --socket=/run/user/1001/rootlesskit/foo/api.sock remove-ports 1
1
You can also expose the ports manually without using the API socket.
$ pid=$(cat /run/user/1001/rootlesskit/foo/child_pid)
$ socat -t -- TCP-LISTEN:8080,reuseaddr,fork EXEC:"nsenter -U -n -t $pid socat -t -- STDIN TCP4\:127.0.0.1\:80"
Routing ping packets
To route ping packets, you need to set up net.ipv4.ping_group_range
properly.
$ sudo sh -c "echo 0 2147483647 > /proc/sys/net/ipv4/ping_group_range"
Note: routing ping packets is not supported for --net=vpnkit
.
Annex: benchmark (MTU=1500)
Aug 1, 2018, on Travis: https://travis-ci.org/rootless-containers/rootlesskit/builds/410721610
--net=slirp4netns
: 1.07 Gbits/sec--net=vpnkit
: 528 Mbits/sec--net=vdeplug_slirp
: 771 Mbits/sec
Note: slirp4netns can reach 8.18 Gbits/sec with MTU=65520: https://github.com/rootless-containers/slirp4netns/pull/20
Annex: how to install slirp4netns
(required for --net=slirp4netns
)
See also https://github.com/rootless-containers/slirp4netns
$ git clone https://github.com/rootless-containers/slirp4netns
$ cd slirp4netns
$ ./autogen.sh && ./configure && make
$ cp slirp4netns ~/bin
RPM is also available for Fedora: https://rpms.remirepo.net/rpmphp/zoom.php?rpm=slirp4netns
$ sudo dnf install slirp4netns
Annex: how to install VPNKit (required for --net=vpnkit
)
See also https://github.com/moby/vpnkit
$ git clone https://github.com/moby/vpnkit.git
$ cd vpnkit
$ make
$ cp vpnkit.exe ~/bin/vpnkit
Annex: how to install vdeplug_slirp
(required for --net=vdeplug_slirp
)
You need to install the following components:
- https://github.com/rd235/s2argv-execs
- https://github.com/rd235/vdeplug4 (depends on
s2argv-execs
) - https://github.com/rd235/libslirp
- https://github.com/rd235/vdeplug_slirp (depends on
vdeplug4
andlibslirp
)
Please refer to README in the each of the components.