Skip to main content

My LXC crash course:

Remember chroot? Container is far beyond a chrooted environment. Think of it as an isolated subsystem in a host OS, which allows running processes in complete isolation - even the hardware visible to the container is virtualized. Containers typically take much less resources than a full virtual machine because containers leverage features in host OS to facilitate isolation.

LXC is one such user interface that leverages containment features in Linux kernel and allows creation and management of containers. Each container running on the same Linux host can run a separate linux distribution. Amazing isn't it?

Containers come in very handy to create isolated environments which do not take up as much resources as running separate virtual machines do. You can use containers to host multiple web services in isolation on a single system. Another good use could be to create multiple development environments.

To create a container in LXC, you first need to have LXC installed on your Linux distribution. Once you have LXC installed, you can type this command to create a container:
lxc-create -t download -n my-container
The download template will list available distributions to choose from. Shortly after you make a choice, your container will be ready to run your selected distribution.

To start your container:
lxc-start -n my-container -d
You can check its status by a couple methods:
lxc-info -n my-container
lxc-ls -f
To drop to shell inside your container environment:
lxc-attach -n my-container
To stop the container:
lxc-stop -n my-container
To remove the container:
lxc-destroy -n my-container
Containers are fun. If you have not yet played around with containers, you should.
Disclaimer: If you follow the information here, there is no warranty, I am not liable if it deletes your data, gets you hacked, burns your house down or anything else. If you follow the information contained here you do so entirely at your own risk.  My views and opinions are my own and not necessarily represent the views of my current or former employers.

© Raheel Hameed and, 2017. Unauthorized use and/or duplication of this material without express and written permission from this site’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to author and this website with appropriate and specific direction to the original content.


Popular posts from this blog

Recovery: Your PC/Device needs to be repaired

If you see this message when you boot your Windows 10, there is something you can do to fix. Read below. "Recovery Your PC/Device needs to be repaired Error code: 0xc0000225" All it is saying is that system startup boot information is somehow messed up. But it is an easy fix. You need a Windows 10 installation media or Recovery media. Boot from the media you have. Then navigate to Troubleshoot, and then choose Advanced, and then Command Prompt. At prompt, change current directory to: cd c:\ Then run these commands one by one to repair your boot sequence: bootrec /fixboot bootrec /fixmbr bootrec /rebuildbcd During these steps it may ask you if a particular Windows partition is the right one to boot into, choose yes if it is. Remove your recovery media, and reboot your computer. It should boot fine.

Using XPerf

XPerf comes with Windows SDK. You can get it from MSFT website. During installation there is an option to install just the performance tools should you want only perf tools and not the whole SDK. To collect a trace from administrator command line: Begin your workload. xperf -on base+cswitch+power -stackwalk Profile -f c:\kernel.etl  Let the workload execute for a while. xperf -stop  If you have previously created c:\merged.etl, delete it. xperf -merge c:\kernel.etl c:\merged.etl  Now, before you can view your trace in UI, setup your symbol path: set _NT_SYMBOL_PATH=<path to PDB files>  You should now be all set to launch the viewer: xperf c:\merged.etl (this launches the viewer)  On the UI, there are several different type of graphs for various measurements. From inside the Graph menu, you can enable these views: CPU Usage by Process. CPU Sampling by CPU. Stack Counts by type. Happy XPerf-ing!

Backup and Restore SVN Repository

SVN provides a simple way to backup or export SVN repository along with modification history. To export repository located at /mnt/svn/branches to a file "dump_file", you would write: svnadmin dump --incremental --deltas /mnt/svn/branches >~/dump_file On the other SVN server, you can restore the entire repository along with the modification history by doing this: svnadmin create --pre-1.6-compatible /mnt/svn/branches svnadmin load /mnt/svn/branches <~/dump_file The first line will create a new empty repository. You can remove --pre-1.6-compatible flag if you like. It's needed only if you want to make your repository compatible with previous versions of SVN. The second line restores your repository from "dump_file". Hurray! Now you can move your SVN repository to the other server without loosing your change history.