Image build optomization + No SSH Access

[faddat]

So I've recently decided to move our image generator for Starport from Ubuntu to Arch, mainly because of the better package support.


I am using packer-builder-arm to do some configuration on what becomes the device image in a chroot

Key files for this are:

https://github.com/faddat/starport/blob ... -image.yml

https://github.com/faddat/starport/blob ... rport.json

Is it possible that bringing it up in the chroot is suppressing the usual generation of an SSH keypair that would come up at boot?

The symptom is pretty simple:

I don't get an SSH service on 22 when it boots.

technically there are a couple of other problems with my approach as well, I run the Pac-Man key gen so that I can fetch various packages and I was wondering about cleaning that out as well.

In the end state, this needs to provide the user with an entirely plug and play experience, because we're actually doing here is replacing several hours of configuration per node by shipping the software as hardware.

My hope is that I can figure out an optimal process for creating these images. I think it's perfectly possible that my current process is not optimal.

Maybe it is better to just copy things into the file system?

Also I'm curious where the build scripts are for the Arch Linux arm images. I am working with 64 bit raspberry Pi 4 tarball currently.