Skip to main content

First 3 Days with bootc

I decided to spend some time playing with bootc. Mostly I'm inspired by the following articles: 


Day 1

To install bootc in a VM I need an image. bootc-image-builder requires root and I don't want to run this on the host. So I chose CoreOS as the inital system and installed it to QEMU.

I thought it is a great idea to share a folder from host to guest as podman container storage. However, it was not as smooth as I had expected:

  • virtiofsd on Debian is too old, so I set up NFS.
  • rootless podman doesn't work well with NFS.
  • rootfull podman complains upstream fs of overlayfs missing features, the performance was terrible.
I gave up. I guess I'll just use the CoreOS disk, whose size is 10G, not enough.


Day 2

I didn't find a way of resizing a qcow2 image online. On the other hand I figured maybe I don't need build a disk image after all. CoreOS is already based on ostree, maybe I can use `bootc switch`. This is essentially the same approach as in the first blog post.

`bootc switch` just works, it can reboot, but I cannot login (ssh or local). Fortunately (and quite nicely), I can rollback ostree even without logging in, because I can do that with grub.

I suspect it is because some files are overriding the files in the image.


Day 3

I learned that QEMU has builtin samba support, which is much easier to use than NFS.

Eventually I found that it was SELinux that has been messing up. With `restorecon -R` I could login from QEMU terminal, but not ssh. After logging in, `bootc status` threw an error about /boot, so I guess I needed `bootc install` afte rall.

So I just went back to the original solution, just resize the CoreOS image and build bootc image inside CoreOS. It worked this time.

Now I need to complete the loop, the new bootc OS should build itself and automatically update itself. And a few more things to fix:

- /etc/fstab does not work if modified when building the container, I need to create systemd mount files for mounts

- /etc/hostname does not work if modified when building the container, I need to set it after each boot

- Unlike `bootc install`, `bootc-image-builder` does not provide flags to override the bootc repository, so I need to set it after boot

- Transient etc sounds like a good idea, but I'll need to manually configure /boot. I'd like to enable it when the official doc explains more details.


Conclusion:

bootc works and its quite fun. But unfortunately I didn't find a way of actually using it in production yet:

  • I could put it into a VM, but sharing files between host and VM is not pretty at the moment (on Debian stable)
  • I don't trust it as my main server yet, and I don't have other machine to which I can install bootc bare-metal.

I think later I'll spend more time trying to tinker with it.

Labels:

Comments

Post a Comment

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »

Installing Linux on Surface Pro 1g

Windows 10 will soon reach its end of life, and my 1-gen Surface Pro is not supported by Windows 11. I (finally) decided to install Linux to it. Fortunately, it's a not-so-easy nice adventure: The device has only one USB port, so I have to bring back my 10+-year old USB hub. My live USB drive cannot boot directly, I have to disable Secure Boot first, by holding Volume Up during boot. I think years ago I learned that booting on USB might not work through a USB hub, but fortunatelly it worked well with my setup. This is done by holding Volume Down during boot. Wifi adapter was detected in the live Linux environment, but not functional. And I don't have a USB-Ethernet adapter. Luckily, nowadays we have USB-tethering from Android phones, which works out-of-the-box. Originally I planned to following this guide to set up root on ZFS, however, the system froze when building the ZFS kernel module. Then I decided to just use EXT4, yet I still learned a lot from the guide about disk par...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »