<div>
Thanks,<br />
so will I allocate RAM or HD Space to a container?
</div>


<div>
Yes, but the disk space is a subdirectory on your existing disk... &nbsp;(that sub directory is the &quot;root&quot; for the container.<br />
(The container cannot go upwards; the host can go into the container directories).<br />
All processes &quot;inside&quot; the container share the RAM with the host. (they are part of the host page tables etc.).<br />
Within the container the uid 0 is NOT uid 0 in the host. (there is a renumbering schema). <br />
Same for PID's so a process list inside the container is different from outside of the container. (try a ps command on both).<br />
One container will not see, be able to access processes &amp;&nbsp;data from another container or the host.
</div>


<div>
Much depends on your needs. The point noci made.<br />
Lxds operate at host resource level, while VMs are guests and depend on scheduling by a hypervisor allocating resources between/among VMs.<br />
<br />
<br />
The container provides some isolation compared to a straight forward shared hosting. I.e. DDoS on one site, impacts all, while in the lxd, the impact could be limited to the site/sites within the container only.<br />
<br />
VMs you have/consume more since you have to install the os, conf...
</div>


<div>
Thanks guys one last question - do I need to give each LXD their own IP Address, or is it sufficient to use IP Tables to forward the request to the container's local IP Address?
</div>


<div>
the LXD daemon (runs once..., has one address).... it starts LXC environments..<br />
that can have private nets, natted nets, bridged nets...<br />
<br />
LXD is the management interface.. (if you compare to XEN, &nbsp; the Dom0..., and DomU's are done through LXC).
</div>


<div>
LXD has it own private netwok, which include the network configuration like bridge, nat,.<br />
For outside access to map to internal network address to the container.<br />
Hope this will help you
</div>


<div>
<div class="content wysiwyg-content">
I was wondering some basic things about LDX containers (how they are different from virtual machines) and also why they would be preferred for shared web hosting:<br />
<br />
So as far as differences between VMs - do you allocate a certain amount of RAM or HD space to them? Or can you set them and they scale?<br />
<br />
Why would they be preferred for shared web hosting? It seems like there would be some security benefits. Would it guarantee some performance if one site got a ton of traffic?<br />
<br />
Would there be any disadvantages to running LDX containers?
</div>
</div>


I was wondering some basic things about LDX containers (how they are different from virtual machines) and also why they would be preferred for shared web hosting:

So as far as differences between VMs - do you allocate a certain amount of RAM or HD space to them? Or can you set them and they scale?

Why would they be preferred for shared web hosting? It seems like there would be some security benefits. Would it guarantee some performance if one site got a ton of traffic?

Would there be any disadvantages to running LDX containers?

Difference between LDX containers and VMs

Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.

Linux

Security is the protection of information systems from theft or damage to the hardware, the software, and the information on them, as well as from disruption or misdirection of the services they provide. The main goal of security is protecting assets, and an asset is anything of value and worthy of protection.  Information Security is a discipline of protecting information assets from threats through safeguards to achieve the objectives of confidentiality, integrity, and availability or CIA for short. On the other hand, disclosure, alteration, and disruption (DAD) compromise the security objectives.