Jeremy Davis's picture

Great work. Really glad to hear that you got it running! Re the previous suggestions I had, I've opened an issue on our issue tracker so it doesn't get forgotten. I'll aim to have it updated at least by our next release (although ideally sooner).

So let me see if I get you straight, you're suggesting an (interactive) script which the user could run which could:

  • allow setting a common password (and thus avoid the requirement of generating an inithooks file)
  • set the hostname. TBH, not sure if we'd need that?! IIRC the name you give the appliance automatically becomes the hostname doesn't it?!
  • set networking - bridged or NAT

WRT naming this script, we have a precedent of prefixing TurnKey specific scripts with turnkey- (e.g. turnkey-version). I'd be inclined to stick with that precedent. Although we could provide an alternate name starting with lxc- (probably including turnkey or tkl in the name too to make it clear where it comes from).

If we were to develop this script, my inclination would be to allow it to accept arguments (e.g. --password) (so it could run non-interactively). But any arguments not supplied would be asked. Perhaps to add value, it would also start the freshly created/configured container?

TBH, I'm not sure if/when we'll get to that, but in essence I think it's quite a cool idea. If you want to hone your bash skills, then perhaps it's something you might want to have a crack at?! :)