README.md

   1 # lxcfs
   2
   3 ## Introduction
   4 LXCFS is a small FUSE filesystem written with the intention of making Linux
   5 containers feel more like a virtual machine. It started as a side-project of
   6 `LXC` but is useable by any runtime.
   7
   8 LXCFS will take care that the information provided by crucial files in `procfs`
   9 such as:
  10
  11 ```
  12 /proc/cpuinfo
  13 /proc/diskstats
  14 /proc/meminfo
  15 /proc/stat
  16 /proc/swaps
  17 /proc/uptime
  18 /proc/slabinfo
  19 /sys/devices/system/cpu
  20 /sys/devices/system/cpu/online
  21 ```
  22
  23 are container aware such that the values displayed (e.g. in `/proc/uptime`)
  24 really reflect how long the container is running and not how long the host is
  25 running.
  26
  27 Prior to the implementation of cgroup namespaces by Serge Hallyn `LXCFS` also
  28 provided a container aware `cgroupfs` tree. It took care that the container
  29 only had access to cgroups underneath it's own cgroups and thus provided
  30 additional safety. For systems without support for cgroup namespaces `LXCFS`
  31 will still provide this feature but it is mostly considered deprecated.
  32
  33 ## Upgrading `LXCFS` without restart
  34
  35 `LXCFS` is split into a shared library (a libtool module, to be precise)
  36 `liblxcfs` and a simple binary `lxcfs`. When upgrading to a newer version of
  37 `LXCFS` the `lxcfs` binary will not be restarted. Instead it will detect that
  38 a new version of the shared library is available and will reload it using
  39 `dlclose(3)` and `dlopen(3)`. This design was chosen so that the fuse main loop
  40 that `LXCFS` uses will not need to be restarted. If it were then all containers
  41 using `LXCFS` would need to be restarted since they would otherwise be left
  42 with broken fuse mounts.
  43
  44 To force a reload of the shared library at the next possible instance simply
  45 send `SIGUSR1` to the pid of the running `LXCFS` process. This can be as simple
  46 as doing:
  47
  48     kill -s USR1 $(pidof lxcfs)
  49
  50 ### musl
  51
  52 To achieve smooth upgrades through shared library reloads `LXCFS` also relies
  53 on the fact that when `dlclose(3)` drops the last reference to the shared
  54 library destructors are run and when `dlopen(3)` is called constructors are
  55 run. While this is true for `glibc` it is not true for `musl` (See the section
  56 [Unloading libraries](https://wiki.musl-libc.org/functional-differences-from-glibc.html).).
  57 So users of `LXCFS` on `musl` are advised to restart `LXCFS` completely and all
  58 containers making use of it.
  59
  60 ## Building
  61 Build lxcfs as follows:
  62 > Notes:In some operating systems, fuse3 is required for compilation, not fuse.
  63 >
  64 >For example: yum install fuse3 fuse3-libs fuse3-devel
  65
  66     yum install fuse fuse-libs fuse-devel
  67     git clone git://github.com/lxc/lxcfs
  68     cd lxcfs
  69     ./bootstrap.sh
  70     ./configure
  71     make
  72     make install
  73
  74 ## Usage
  75 The recommended command to run lxcfs is:
  76
  77     sudo mkdir -p /var/lib/lxcfs
  78     sudo lxcfs /var/lib/lxcfs
  79
  80 A container runtime wishing to use `LXCFS` should then bind mount the
  81 approriate files into the correct places on container startup.
  82
  83 ### LXC
  84 In order to use lxcfs with systemd-based containers, you can either use
  85 LXC 1.1 in which case it should work automatically, or otherwise, copy
  86 the `lxc.mount.hook` and `lxc.reboot.hook` files (once built) from this tree to
  87 `/usr/share/lxcfs`, make sure it is executable, then add the
  88 following lines to your container configuration:
  89 ```
  90 lxc.mount.auto = cgroup:mixed
  91 lxc.autodev = 1
  92 lxc.kmsg = 0
  93 lxc.include = /usr/share/lxc/config/common.conf.d/00-lxcfs.conf
  94 ```
  95
  96 ## Using with Docker
  97
  98 ```
  99 docker run -it -m 256m --memory-swap 256m \
 100       -v /var/lib/lxcfs/proc/cpuinfo:/proc/cpuinfo:rw \
 101       -v /var/lib/lxcfs/proc/diskstats:/proc/diskstats:rw \
 102       -v /var/lib/lxcfs/proc/meminfo:/proc/meminfo:rw \
 103       -v /var/lib/lxcfs/proc/stat:/proc/stat:rw \
 104       -v /var/lib/lxcfs/proc/swaps:/proc/swaps:rw \
 105       -v /var/lib/lxcfs/proc/uptime:/proc/uptime:rw \
 106       -v /var/lib/lxcfs/proc/slabinfo:/proc/slabinfo:rw \
 107       ubuntu:18.04 /bin/bash
 108  ```
 109
 110  In a system with swap enabled, the parameter "-u" can be used to set all values in "meminfo" that refer to the swap to 0.
 111
 112  sudo lxcfs -u /var/lib/lxcfs
 113
 114 ## Swap handling
 115 If you noticed LXCFS not showing any SWAP in your container despite
 116 having SWAP on your system, please read this section carefully and look
 117 for instructions on how to enable SWAP accounting for your distribution.
 118
 119 Swap cgroup handling on Linux is very confusing and there just isn't a
 120 perfect way for LXCFS to handle it.
 121
 122 Terminology used below:
 123  - RAM refers to `memory.usage_in_bytes` and `memory.limit_in_bytes`
 124  - RAM+SWAP refers to `memory.memsw.usage_in_bytes` and `memory.memsw.limit_in_bytes`
 125
 126 The main issues are:
 127  - SWAP accounting is often opt-in and, requiring a special kernel boot
 128    time option (`swapaccount=1`) and/or special kernel build options
 129    (`CONFIG_MEMCG_SWAP`).
 130
 131  - Both a RAM limit and a RAM+SWAP limit can be set. The delta however
 132    isn't the available SWAP space as the kernel is still free to SWAP as
 133    much of the RAM as it feels like. This makes it impossible to render
 134    a SWAP device size as using the delta between RAM and RAM+SWAP for that
 135    wouldn't account for the kernel swapping more pages, leading to swap
 136    usage exceeding swap total.
 137
 138  - It's impossible to disable SWAP in a given container. The closest
 139    that can be done is setting swappiness down to 0 which severly limits
 140    the risk of swapping pages but doesn't eliminate it.
 141
 142 As a result, LXCFS had to make some compromise which go as follow:
 143  - When SWAP accounting isn't enabled, no SWAP space is reported at all.
 144    This is simply because there is no way to know the SWAP consumption.
 145    The container may very much be using some SWAP though, there's just
 146    no way to know how much of it and showing a SWAP device would require
 147    some kind of SWAP usage to be reported. Showing the host value would be
 148    completely wrong, showing a 0 value would be equallty wrong.
 149
 150  - Because SWAP usage for a given container can exceed the delta between
 151    RAM and RAM+SWAP, the SWAP size is always reported to be the smaller of
 152    the RAM+SWAP limit or the host SWAP device itself. This ensures that at no
 153    point SWAP usage will be allowed to exceed the SWAP size.
 154
 155  - If the swappiness is set to 0 and there is no SWAP usage, no SWAP is reported.
 156    However if there is SWAP usage, then a SWAP device of the size of the
 157    usage (100% full) is reported. This provides adequate reporting of
 158    the memory consumption while preventing applications from assuming more
 159    SWAP is available.