Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using docker container to run legacy brickstrap #70

Open
BrendanSimon opened this issue Jul 17, 2020 · 0 comments
Open

Using docker container to run legacy brickstrap #70

BrendanSimon opened this issue Jul 17, 2020 · 0 comments

Comments

@BrendanSimon
Copy link
Contributor

BrendanSimon commented Jul 17, 2020

Is it possible to use a Docker container (e.g. running Debian Buster) to run the legacy brickstrap to generate a rootfs ?

My current setup is a Debian Jessie install on a VirtualBox VM (on my Mac). It's time to upgrade.

I initially was going to migrate to a Debian Buster (or Unbuntu 20.04) distro on a VirtualBox VM (on a Windows 10 laptop).

I'm sure that would work, however I thought maybe using Docker and Hyper-V would be lighter and faster. I managed to install an Debian Buster container, with various tool, cloned my frozen brickstrap repo and tried to build.

I got stuck in these places.

  • key errors with multistrap
  • installing libguestfs requires lvm2, which just hangs during install.
  • no /boot/vmlinuz* files required by guestfs
Get:1 http://deb.debian.org/debian buster InRelease [121 kB]
Err:1 http://deb.debian.org/debian buster InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY DCC9EFBF77E11517
Reading package lists... Done
W: GPG error: http://deb.debian.org/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY DCC9EFBF77E11517
E: The repository 'http://deb.debian.org/debian buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
apt update failed. Exit value: 100

I think the install scripts for lvm2 are trying to determine a runlevel but Docker containers are not runlevel aware as they don't run systemd (this is as far as I can workout from good old googling).

So is this thing going to fly or am I better off just running a full Debian or Ubuntu OS in a VM ?

NOTE: this is a first step so I don't break my current build with the legacy brickstrap. After that I want to try the new brickstrap.

Thanks, Brendan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant