“Running with unpopulated /etc” – Failing to run systemd based container ?

Recently I experienced, systemd based container fails to run in certain version of distros.

For ex: If I run my container with systemd I get below messages.

#docker run –rm -t -i –privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro

systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Detected virtualization docker.
Detected architecture x86-64.
Running with unpopulated /etc.
....
Set hostname to .
Initializing machine ID from random generator.
Populated /etc with preset unit settings.
Unit etc-hosts.mount is bound to inactive unit dev-mapper-X.X.root.device. Stopping, too.
Unit etc-hostname.mount is bound to inactive unit dev-mapper-X.X.root.device. Stopping, too....
Unit etc-resolv.conf.mount is bound to inactive unit dev-mapper-X.X.root.device. Stopping, too.
Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Startup finished in 106ms.
Failed to create unit file /run/systemd/generator.late/network.service: File exists
Failed to create unit file /run/systemd/generator.late/netconsole.service: File exists

The line ‘Running with unpopulated /etc’ looked suspicious to me, after some attempts we were able to conclude that, the things were going wrong in absense of ‘/etc/machine-id’ file which used to be there. If you came across similar to this situation, make an entry in your docker file to create /etc/machine-id as shown below and give a try!

#RUN touch /etc/machine-id

now, build your image and start the container from new image.. Let me know how it goes.

Fedora 20 beta release (Heisenbug) announcement and 10th year of selinux!

I would like to share this news with you guys..

The Fedora Project announced the beta release of Fedora 20, code-named “Heisenbug.” A community-produced, free, Linux-based operating system, Fedora 20 features some of the latest and best of what the open source world has to offer.

You can read more about this release announcement at below urls.

www.redhat.com/about/news/archive/2013/11/fedora-20-heisenbug-now-available-in-beta-release#!

lwn.net/Articles/573588/

From cloud and virt point of view, this release includes:

Secondly, selinux is celebrating its 10th year with an awesome how-to guide for SELinux policy enforcement ..

If you havent got ‘selinux’ yet, please go through the ‘visual treat’ here..

opensource.com/business/13/11/selinux-policy-guide

Install bit torrent client ( transmission) for fedora ..

Friday or drive by post here 🙂

How to install and use bit torrent clients in fedora? its as simple as that: You need to install ‘transmission’ package to get bit torrent client for fedora.
Once you installed it, bit torrent client is ready to use for torrent action. You can either use ‘transmission” cli or GUI mode.

‘transmission-cli-2.80-2.fc19.x86_64’ provides ‘cli’ version of torrent client.

You can use above switches of the binary for torrent actions.

If you are interested in graphical utility of torrent client , its provided by ‘transmission-gtk-2.77-3.fc19.x86_64’ package :

You can either run :

#/usr/bin/transmission-gtk

or download ‘torrent’ file, then open it with ‘transmission’ :

You are done..

Smooth upgrade from fedora 18 to fedora 19 !

I always failed to do a streaming update from earlier versions of fedora, but not this time. That said, I had fedora 18 version installed in my system and planned to upgrade to latest verison of fedora 19 named “Fedora release 19 (Schrödinger’s Cat) ” 🙂

Without much intro, let me share the steps I followed here:

1) If you have any other repositories configured ( inside /etc/yum.repos.d) other than fedora repos , please disable others. It may not be necessary, but I did that to make my upgrade smooth.

2)Then make sure you are running latest version of ‘yum’ and ‘rpm’ in your system.

Make sure it via:

2) Once its done, update all the packages and make sure you are running latest version of fedora 18 packages in your system : This is a must process.

3) Lets clear the “cache” by running

Now you may be running the older version of fedora 18 kernel in your system: lets boot the system into the latest kernel. If you are already with the latest its fine.

4) Once you are back with the latest kernel, you need to install the package called ‘fedup’

Above excerpt give required info about the tool.

Once its installed there is a binary called , ‘fedup-cli’ and it got below options with it:

Location to search for upgrade data.

We are going to use ‘–network’ option with it:

Now it will perform Step [1] steps as mentioned above:

Then it will instruct you to reboot the system :

Once you are in grub menu , you will be provided with the option of “fedup-upgrade” menu , select it, so that it will perform the Step [2] part of it which is the actual upgrade process and you can go for ‘dinner’ 🙂

Upon completion of Step [3] the system will be rebooted and once you login :

You may see something like this :

Let me know how smooth it was for you 🙂

What is “BIOS BOOT” filesystem type in fedora and why it is required ?

Today while installing Fedora-18 , I noticed an error at installation window ( the place where you define storage partitions). The installer option “begin installation” at bottom of the window was greyed out. By Clicking the error message details from the anaconda screen, I was told that, it is missing “BIOS BOOT” filesystem type.

So, why BIOS BOOT is required and what is that ?

Starting in Fedora 16, on non-EFI x86 (32 and 64 bit) systems, anaconda will default to creating GPT disklabels (partition tables) instead of MSDOS disklabels. On these systems, when booting from a GPT-labelled disk, it is strongly recommended (not necessarily required in all cases, depending on the system’s BIOS/firmware) to create a small (1MiB) BIOS boot partition. This partition will be used by the bootloader (GRUB2) for storage.
Automatic partitioning will create the partition when appropriate, but users who choose custom partitioning will have to create this partition for themselves.
This BIOS boot partition is only necessary on non-EFI x86 systems whose boot device is a GPT-labelled disk.

Please note that , BIOS BOOT is a filesystem type.

After creating that parition I was able to perform/proceed with the installation of fedora 18.

Install 64 bit skype in fedora16

I will conclude the steps here:
1) Download 64 bit version of skype by below command

2) From the downloaded directory, do

Now, skype should be installed in your system, once it is installed , run

#skype

Stage is yours!!! Njoy…