+[](https://linuxcontainers.org/lxd)
# LXC
-* Jenkins: [](https://jenkins.linuxcontainers.org/job/lxc-github-commit/)
-* Travis: [](https://travis-ci.org/lxc/lxc/)
-
LXC is the well-known and heavily tested low-level Linux container runtime. It
is in active development since 2008 and has proven itself in critical
production environments world-wide. Some of its core contributors are the same
people that helped to implement various well-known containerization features
inside the Linux kernel.
+## Status
+Type | Service | Status
+--- | --- | ---
+CI (Linux) | GitHub | [](https://github.com/lxc/lxc/actions)
+CI (Linux) | Jenkins | [](https://jenkins.linuxcontainers.org/job/lxc-github-commit/)
+Project status | CII Best Practices | [](https://bestpractices.coreinfrastructure.org/projects/1087)
+Code Quality | LGTM | [](https://lgtm.com/projects/g/lxc/lxc/context:cpp)
+Fuzzing | OSS-Fuzz | [](https://oss-fuzz-build-logs.storage.googleapis.com/index.html#lxc)
+Fuzzing | CIFuzz | [](https://github.com/lxc/lxc/actions/workflows/cifuzz.yml)
+
## System Containers
LXC's main focus is system containers. That is, containers which offer an
LXC namespaces configuration keys by using single dots. This means complex
configuration keys such as `lxc.net.0` expose various subkeys such as
-`lxc.net.0.type`, `lxc.net.0.link`, `lxc.net.0.ipv6`, and others for even
-more fine-grained configuration.
+`lxc.net.0.type`, `lxc.net.0.link`, `lxc.net.0.ipv6.address`, and others for
+even more fine-grained configuration.
LXC is used as the default runtime for [LXD](https://github.com/lxc/lxd),
a container hypervisor exposing a well-designed and stable REST-api on top of
- i686
- x86_64
- ppc, ppc64, ppc64le
+- riscv64
- s390x
- armvl7, arm64
LXC has always focused on strong backwards compatibility. In fact, the API
hasn't been broken from release `1.0.0` onwards. Main LXC is currently at
-version `2.*.*`.
+version `4.*.*`.
## Reporting Security Issues
efficiently. If you think you've found a potential security issue, please
report it by e-mail to all of the following persons:
-- serge.hallyn (at) ubuntu (dot) com
+- serge (at) hallyn (dot) com
- stgraber (at) ubuntu (dot) com
-- christian.brauner (at) ubuntu (dot) com
+- brauner (at) kernel (dot) org
For further details please have a look at
repo.
If you want to become more active it is usually also a good idea to show up in
-the LXC IRC channel `#lxc-dev` on `Freenode`. We try to do all development out
+the LXC IRC channel [#lxc-dev](https://kiwiirc.com/client/irc.libera.chat/#lxc-dev) on irc.libera.chat. We try to do all development out
in the open and discussion of new features or bugs is done either in
-appropriate Github issues or on IRC.
+appropriate GitHub issues or on IRC.
When thinking about making security critical contributions or substantial
changes it is usually a good idea to ping the developers first and ask whether
Source for the latest released version can always be downloaded from
-- https://linuxcontainers.org/downloads/
+- https://linuxcontainers.org/lxc/downloads/
You can browse the up to the minute source code and change history online
Without considering distribution specific details a simple
- ./autogen.sh && ./configure && make && sudo make install
+ meson setup -Dprefix=/usr build
+ meson compile -C build
is usually sufficient.
-In order to test current git master of LXC it is usually a good idea to compile with
-
- ./autogen.sh && ./configure && make
-
-in a convenient directory and set `LD_LIBRARY_PATH="${BUILD_DIR}"/lxc/src/lxc/.libs`.
-
## Getting help
When you find you need help, the LXC projects provides you with several options.
### Discuss Forum
-We maintain an discuss forum at
+We maintain a discuss forum at
- https://discuss.linuxcontainers.org/
where you can get support.
### IRC
-
-You can find support by joining `#lxcontainers` on `Freenode`.
+You can find us in [#lxc](https://kiwiirc.com/client/irc.libera.chat/#lxc) on irc.libera.chat.
### Mailing Lists
projects / mirror_lxc.git / blobdiff