...
LXC is in between a VM and a pure application container. It will take up more resources than a pure container, but unlike a VM use as much memory as needed. It will provide a full kernel and OS (albeit it must be Linux). Unlike a VM, LXD container will have access to the resources and speed of the hardware without needing to emulate hardware. If LXC is the foundation for Cloud Foundry Cloud. Even if you are just interested in Docker or Cloud , and not yet ready to give up your ssh console, start here. Learning LXC, you'll also really understand how Cloud Foundry, Docker and generally Cloud concepts actually works under the hoods.
| Panel |
|---|
What about LXD? LXD is another higher level layer on top of LXC that is more orchestration friendly. The key enablement for orchestration is remote API calls and higher level functions. LXD still uses LXC under the hoods. As of Oct 2016, LXD 2.0 is now available and hooking up with orchestration via Juju. This tutorial was originally written before LXD was ready for production and evolved to be the precursor to the LXD tutorial. |
...
Specify static IPs per container name (you can also use the container's mac address in situations of multiple network interfaces) (I have not tried or tested yet). To avoid conflicts, make sure the static IP addresses are outside of the range specified in /etc/default/lxc-net. In case of multiple ip addresses look at LXC Advanced Networking.
You need to shutdown your containers and then restart the Host OS or flush the DNS Mask,
...
The nice thing about this approach is that the servers within the private network can see each other by assigned hostname. Try pinging by hostname and it will respond correctly. In the case two network cards though, there is some routing work that I have yet to figure out.
...
Containers may also be made available on the larger network which is covered in 5.1 LXC with Advanced Networking - Exposing Containers to the Network.
Start Container
This starts the container as a process,
...