This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
grub_install: Add LOOP_NO_UDEV for builds in a container
A lot of the SDK instructions seem to assume you're in a "classic" Linux login session. I use Fedora Atomic Workstation and do all of my development in "dev containers" (currently docker, in the process of switching to podman). In my setup the `/dev` setup is separate and won't pick up udev changes. (Ideally I'd filter out a lot of host devices, that's another issue) Anyone in a similar situation (which I assume would also include trying to do the SDK build inside a Docker container on CoreOS) can do: `env LOOP_NO_UDEV=1 ./build_images.sh` to have it manually set up the partition mounts. Loopback mounts with containers in general are ugly since they're not namespaced. A whole better solution to this IMO is to use something like http://libguestfs.org/ which basically spawns a VM, although it doesn't support grub2. So we'd really have to do instead something like what Fedora does with using Anaconda. Or the "helper VM" could probably just be an existing CoreOS qcow2.
- Loading branch information