Debian

Posted by stylesen

Introduction, Details and Preparation

Linaro Automated Validation Architecture a.k.a LAVA project has released official docker images for lava-dispatcher only containers. This blog post series explains how to use these images in order to run inpdependent LAVA workers along with devices attached to it. The blog post series is split into three parts as follows:

  1. lava-dispatcher docker images - part 1 - Introduction, Details and Preparation
  2. lava-dispatcher docker images - part 2 - Docker based LAVA Worker running pure LXC job
  3. lava-dispatcher docker images - part 3 - Docker based LAVA Worker running Nexus 4 job with and without LXC Protocol

Before getting into the details of running these images, let us see how these images are organized and what are the packages available via these images.

The lava-dispatcher only docker images will be officially supported by the LAVA project team and there will be regular releases of these images whenever there are updates or new releases. As of this writing there are two images released - production and staging. These docker images are based on Debian Stretch operating system, which is the recommended operating system for installing LAVA.

Posted by stylesen

This is part 2 of the three part blog post series on lava-dispatcher only docker images. If you haven't read part 1 already, then read it on - https://www.stylesen.org/lavadispatcher_docker_images_part_1

Docker based LAVA Worker running pure LXC job

This is the first use case in which we will look at starting a docker based LAVA worker and running a job that requests a LXC device type. The following command is used to start a docker based LAVA worker,

Posted by stylesen

This is part 3 of the three part blog post series on lava-dispatcher only docker images. If you haven't read part 2 already, then read it on - https://www.stylesen.org/lavadispatcher_docker_images_part_2

Docker based LAVA Worker running Nexus 4 job with LXC protocol

This is the second use case in which we will look at starting a docker based LAVA worker and running a job that requests a Nexus 4 device type with LXC protocol. The following command is used to start a docker based LAVA worker,

Posted by stylesen

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.

Posted by stylesen

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.

Me too Debian!

23 Jul 2015
Posted by stylesen

Debian Powered LogoI 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!

Posted by stylesen

Iceweasel is my primary web browser in Debian Jessie and I use it for Google Hangouts too. Recently a month back one fine day when I was about to start with a meeting after an 'apt-get upgrade' on my Debian machine, Google Hangouts stopped working in Iceweasel. Google marked Iceweasel as an unsupported browser and I was left without an option. Enormous searching asked me to use a different user-agent string to act as a supported browser, which also failed in my case. Even with a changed user-agent string Google rejected my Hangout sessions. I haven't been so very comfortable with Google Chrome web browser (experienced from past usages) and didn't want to try it on my Debian Jessie machines, just for Google Hangouts.