There are many ways in which we can setup networking for LXC containers - simple to highly complex. In this blog post I will get the simple steps required in order to have networking work for LXC containers using libvirt. It is hard to create bridges on WiFi interfaces unless your network foo is high (YMMV), but libvirt makes things simple irrespective of the interface. When your dev box is a laptop and want to use LXC on it, then instead of spending hours to get the networking work with the WiFi or avoid getting stranded to cable when using LXC on the laptop, libvirt comes handy. The steps below are tested on Debian Stretch / Testing / Unstable / Sid - give it a shot on other distros with equivalent packages.
This is a continuation to "Access Android devices from LXC" which explains how to access an Android device from within an LXC container. Android Compatibility Test Suite (CTS) represents the "mechanism" of compatibility for Android devices. It is a suite of tests that are run on an Android device to check compatibility of the device under test. We shall see how we can run CTS within LXC so that we have an option of running CTS from different operating systems and different JAVA versions.
LXC aka Linux Containers are a convenient way to run a light weight Virtual Machine. LXC provides a complete operating system with access to devices attached to host machine. Let us see how we can access an Android device from a LXC instance via adb or fastboot. I assume you have a working LXC with networking setup properly. I am using a LXC named 'test-lxc' which is a Debian sid based container (root@test-lxc:/#) and a Google Nexus 4 as android device with debug mode enabled. My host machine (stylesen@harshu:~$) is a Debian sid based Thinkpad.
I was introduced to Debian Operating System back in my college days somewhere in the year 2003. After almost 12 years of using Debian, today I feel proud to say I ve also contributed back to the Debian Community. Yes, I became a Debian Maintainer this week. Introduced in Debian Project News as a New Contributor - https://www.debian.org/News/weekly/2015/06/ I successfully completed Debian New Maintainer process and officially became a Debian Maintainer this week with my GPG key included in the Debian Maintainer Keyring!
Linaro Automated Validation Architecture popularly called LAVA is composed of different components. One of the core components in the LAVA framework is the lava-server component. LAVA developers in the recent past made sure that lava-server's unit tests are working properly and relevant to current code base. As a developer of LAVA I hit this issue everytime I want to run unit tests for lava-server (when I switch environments), mainly due to postgresql dependency. Following are stuff you need to setup in order to run unit tests in LAVA. (Do not do this production deployment, only recommended for dev mode deployments)
lava-master is the default postgresql user created for administering LAVA related databases. In order to run unit tests, the default postgresql user of LAVA should have permissions to create and drop databases. The test database created by LAVA unit test is called 'test_lava-master'. The 'lava-master' user creates and destroys this 'test_lava-master' database each time the unit tests are run. You must be 'root' user in order to perform the following operations:
This is something very personal and I want the world to know about what is happening in my life! I used to stare at women like these during my college days. Initially I thought they were very beautiful and I wanted to stay away from them. Though, as every man has an instinct to spend a life with such a kind of woman I had my thoughts deep inside me, to have someone like one of them. During college there was at least 10 women inside our college premises, with whom I used to hook around occasionally. After finishing college I used to have many chicks who were slim, beautiful (and you know what) with whom I ve spent a lot of time, but still I missed those kinda women in life.