Day 2 at CoreOS

Rain was all over San Francisco early Tuesday morning, the air was crisp and was only a tinge gloomy. I hopped onto the Muni and BART for another exciting day at CoreOS.

It was rather quite when I arrived, so I took to my computer to and saw the build_package for container linux sdk errors on my screen. Eager to get the day started, I promptly traced the errors up leading to the first one.  Immediately following it, in red font it noted to enable TPM (Trusted Platform Module) in the BIOS. So I did as indicated following this guide I found for my Fedora machine.

Enable TPM for Container Linux

Accessing the BIOS is easy, it is also where you would enable virtualization for uses like KVM and VirtualBox. For Lenovo machines i.e. ThinkPads. Do not confuse F10 with F1.  F10 brings you into a diagnostics dashboard whereas pressing F1 during boot accesses the BIOS.

As several people begin to flow in, Will who sat behind me mentioned that enabling TPM was not necessary and then by probing some more that I was eventually informed that the TPM feature in Container Linux was left unfinished because the main person working on it has left the company but the error/warning to enable TPM was still in build_packages. I was then given this command <code&gtemerge-amd64-usr bash readline ncurses<#&47;code&gt to work around those errors after invoking cork enter to enter into the container linux file system.

Wanting to move on with CoreOS’s installation guide for container linux, I did the given command and would then return to it later (really, I was unsure what this command did). I managed to get to the end of the guide while fixing some issues with the guide doc itself on Github. Through my discussion with Andrew about ignition which diverged to other questions that I found out that `emerge-amd64-usr` is a package manager for Gentoo similar to `apt-get` and that doing `emerge-amd64-usr bash readline ncurses` was really rebuilding bash, readline and ncurses. The printed errors would not have lead me to this solution:

Nor would this log file saved within the container linux file system at:

/build/amd64-usr/var/log/portage/sys-kernel:coreos-kernel-4.16.10:20180522-062028.log

indicated that I needed to do the command that I was given.

First things first, ask before venturing on my own? As in, do I ask then do? or Do I venture first then ask, which I have done here? It took me far longer than I expected it would take but learnt about TPM, KVM and also what Mantle does. If I was given the command I needed straight away, I could have finished going through the container linux guide faster and worked on some other stuff. Either one in this case would have been good I believe.

Aside from getting lunch with the others including Sean and Vikram who are the two other interns here, and also the BlueJeans conference call with the OStools team, I managed to to tweak my bubblemelon.com site and also stumbled upon GopherCon’s diversity scholarship application when I joined the WomenWhoGo channel on Gophers.slack.com after 6pm today.

Write your comment Here

This site uses Akismet to reduce spam. Learn how your comment data is processed.