|
|
757.
|
|
|
Troubleshooting
|
|
|
|
|
Вирішення проблем
|
|
Translated by
Yuri Chornoivan
|
|
|
|
Located in
serverguide/C/virtualization.xml:1787(title) serverguide/C/virtualization.xml:2667(title) serverguide/C/mail.xml:390(title) serverguide/C/mail.xml:1698(title) serverguide/C/dns.xml:375(title)
|
|
|
758.
|
|
|
To view debug information about LXD itself, on a systemd based host use
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1789(para)
|
|
|
759.
|
|
|
journalctl -u LXD
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1794(command)
|
|
|
760.
|
|
|
On an Upstart-based system, you can find the log in <filename>/var/log/upstart/lxd.log</filename>. To make LXD provide much more information about requests it is serving, add '--debug' to LXD's arguments. In systemd, append '--debug' to the 'ExecStart=' line in <filename>/lib/systemd/system/lxd.service</filename>. In Upstart, append it to the <command>exec /usr/bin/lxd</command> line in <filename>/etc/init/lxd.conf</filename>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1799(para)
|
|
|
761.
|
|
|
Container logfiles for container c1 may be seen using:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1809(para)
|
|
|
762.
|
|
|
lxc info c1 --show-log
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1814(command)
|
|
|
763.
|
|
|
The configuration file which was used may be found under <filename> /var/log/lxd/c1/lxc.conf</filename> while apparmor profiles can be found in <filename> /var/lib/lxd/security/apparmor/profiles/c1</filename> and seccomp profiles in <filename> /var/lib/lxd/security/seccomp/c1</filename>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1819(para)
|
|
|
764.
|
|
|
LXC
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1829(title)
|
|
|
765.
|
|
|
Containers are a lightweight virtualization technology. They are more akin to an enhanced chroot than to full virtualization like Qemu or VMware, both because they do not emulate hardware and because containers share the same operating system as the host. Containers are similar to Solaris zones or BSD jails. Linux-vserver and OpenVZ are two pre-existing, independently developed implementations of containers-like functionality for Linux. In fact, containers came about as a result of the work to upstream the vserver and OpenVZ functionality.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1831(para)
|
|
|
766.
|
|
|
There are two user-space implementations of containers, each exploiting the same kernel features. Libvirt allows the use of containers through the LXC driver by connecting to 'lxc:///'. This can be very convenient as it supports the same usage as its other drivers. The other implementation, called simply 'LXC', is not compatible with libvirt, but is more flexible with more userspace tools. It is possible to switch between the two, though there are peculiarities which can cause confusion.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/virtualization.xml:1841(para)
|
