Jump to content

Building Armbian with Multipass VMs


atomic77
Go to solution Solved by atomic77,

Recommended Posts

  • Solution

Hello all,

 

I recently went through the exercise of getting the Armbian build system set up to create an image with some of my user customizations, similar to the example with OMV. The documentation and forums have been a huge help!

 

As I am running Fedora and Windows as my main OSes, I did struggle a bit at first. I tried, in order:

 

  • Ignoring the advice of the documentation, and running ./compile.sh on Fedora. Didn't get far :)
  • Running the build with Docker on Fedora. I ran into a number of different problems and ultimately gave up.
  • Running on Ubuntu 18.04 on WSL2. I did eventually get a build to complete, but the image may have been corrupt because my device didn't boot at all
  • Considered using Vagrant, but decided to give Multipass a try. Worked like a charm on the first try on both my environments!

 

I didn't find anything on the forums or documentation about using multipass to manage build VMs, so I decided to create a small gist here documenting how I got it working: https://gist.github.com/atomic77/7633fcdbf99dca80f31fd6d64bfd0565

 

For any not familiar, multipass is a Canonical tool that is optimized for creating Ubuntu VMs, which seems perfect for Armbian since that's the preferred platform anyway. Since it's so focused, it's very simple to use and all the utilities like shared mounts work seamlessly compared to Vagrant.

 

If this could be helpful to others, I'd be happy to incorporate any feedback into a page for the documentation.

Link to comment
Share on other sites

On 10/7/2020 at 4:16 AM, atomic77 said:

If this could be helpful to others, I'd be happy to incorporate any feedback into a page for the documentation.


Officially supported way of building is native Ubuntu, but it also should work well under Docker and natively on other Debian based distribitions. I am running build on Mint and Debian without issues ...

Since you get it working and already made some how-to, I have nothing against to merge this into our documentation - which is anyway our common work, but we should probably clearly say which methods are officially supported and which not? @Werner What do you think?

Link to comment
Share on other sites

Since it is a community contribution for now I suggest to add a link to the gist into the docs and mention it with Vagrant and Docker. This way it can still be enhanced directly by the author @atomic77.

Just let me know if you are fine with that.

 

As for WSL2 (which I got rid of a while ago in favor of Virtualbox) I never tried building an image in that but building kernel images works great. Also with quite decent performance.

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines