The following pull request was submitted through Github.
It can be accessed and reviewed at: https://github.com/lxc/lxd/pull/6984
This e-mail was sent by the LXC bot, direct replies will not reach the author
unless they happen to be subscribed to this list.
=== Description (from pull-request) ===
Signed-off-by: KATOH Yasufumi <ka...@jazz.email.ne.jp>
From 0645895ee4550808f891d262bea417f716ad90e6 Mon Sep 17 00:00:00 2001
From: KATOH Yasufumi <ka...@jazz.email.ne.jp>
Date: Thu, 5 Mar 2020 18:00:40 +0900
Subject: [PATCH] doc: Tweak markdown format for itemization
Signed-off-by: KATOH Yasufumi <ka...@jazz.email.ne.jp>
---
doc/api-extensions.md | 3 +++
doc/container-environment.md | 1 +
doc/instances.md | 1 +
doc/requirements.md | 1 +
4 files changed, 6 insertions(+)
diff --git a/doc/api-extensions.md b/doc/api-extensions.md
index 64c7d92f30..77249b4f68 100644
--- a/doc/api-extensions.md
+++ b/doc/api-extensions.md
@@ -716,6 +716,7 @@ This introduces a new internal `volatile.idmap.current` key
which is
used to track the current mapping for the container.
This effectively gives us:
+
- `volatile.last\_state.idmap` => On-disk idmap
- `volatile.idmap.current` => Current kernel map
- `volatile.idmap.next` => Next on-disk idmap
@@ -779,6 +780,7 @@ This introduces container IP filtering
(`security.ipv4\_filtering` and `security
## resources\_v2
Rework the resources API at /1.0/resources, especially:
+
- CPU
- Fix reporting to track sockets, cores and threads
- Track NUMA node per core
@@ -832,6 +834,7 @@ This introduces support for a new Type field on images,
indicating what type of
## resources\_disk\_sata
Extends the disk resource API struct to include:
+
- Proper detection of sata devices (type)
- Device path
- Drive RPM
diff --git a/doc/container-environment.md b/doc/container-environment.md
index dd91c899e5..69ebb74fbb 100644
--- a/doc/container-environment.md
+++ b/doc/container-environment.md
@@ -9,6 +9,7 @@ LXD spawns whatever is located at `/sbin/init` as the initial
process of the con
This binary should act as a proper init system, including handling re-parented
processes.
LXD's communication with PID1 in the container is limited to two signals:
+
- `SIGINT` to trigger a reboot of the container
- `SIGPWR` (or alternatively `SIGRTMIN`+3) to trigger a clean shutdown of the
container
diff --git a/doc/instances.md b/doc/instances.md
index 526dc5c358..e217700ab9 100644
--- a/doc/instances.md
+++ b/doc/instances.md
@@ -770,6 +770,7 @@ The full list of bit suffixes currently supported is:
- Eibit (1024^6)
The full list of byte suffixes currently supported is:
+
- B or bytes (1)
- kB (1000)
- MB (1000^2)
diff --git a/doc/requirements.md b/doc/requirements.md
index c7dc088349..d3ec5957e0 100644
--- a/doc/requirements.md
+++ b/doc/requirements.md
@@ -33,6 +33,7 @@ LXD uses `dqlite` for its database, to build and setup the
custom
`sqlite3` and `dqlite` needed for it, you can run `make deps`.
LXD itself also uses a number of (usually packaged) C libraries:
+
- libacl1
- libcap2
- libuv1 (for `dqlite`)
_______________________________________________
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel
