New answers tagged lxc
LXC is a little bit better because it can run containers as unpriveleged users. This is not possible (AFAICT) with systemd-nspawn. If you want to know why docker, lxc, and systemd-nspawn are inherently not a solid security mechanism, read this: https://opensource.com/business/14/7/docker-security-selinux. Basically, containers still have access to the kernel ...
No matter the fancy name used here, both are solutions to a specific problem: A better segregation solution than classic Unix chroot. Operating system-level virtualization, containers, zones, or even "chroot with steriods" are names or commercial titles that defines the same concept of userspace separation, but with different features. Chroot was introduced ...
EOF indicates that no further input is to be expected on a resource which possibly provides an endless amount of data (e.g. a stream). This situation is often expressed by writing a single character on the stream (to be defined by the underlying system (likely a OS or runtime environment )). As processes use streams for inter-process communication they need ...
Rather then running this shutdown -h 0 command I'd suggest running halt instead, or running this command from the host, lxc-shutdown -n <name>. Source: 9.5 Monitoring and Shutting Down Containers
Top 50 recent answers are included