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

TurnKey LXD image server #670

Open
JedMeister opened this issue Jul 19, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@JedMeister
Copy link
Member

commented Jul 19, 2016

Spammy on the forums has requested that we host our own LXD server. TBH I'm not 100% sure on the requirements or what is involved but it seems like a cool idea...

@JedMeister

This comment has been minimized.

Copy link
Member Author

commented Oct 18, 2016

bmullan has added some more details with some links etc. It all sounds fairly straight forward so IMO we should definitely consider this!

@JedMeister

This comment has been minimized.

Copy link
Member Author

commented Oct 19, 2016

@jgillich

This comment has been minimized.

Copy link

commented May 14, 2017

See my comment at https://discuss.linuxcontainers.org/t/is-there-a-lxd-hub-in-the-pipleline-anywhere/103/7

Could this be of interest to the TurnKey project? I have no idea how you're currently building images and if you have ever considered Packer, but to me this sounds like a great fit.

@JedMeister

This comment has been minimized.

Copy link
Member Author

commented Jun 14, 2017

Hey @jgillich thanks for your input.

Whilst we've been keeping half an eye on Packer, we've been using our homegrown buildtasks to build to multiple image targets since long before Packer. It's essentially just a bundle of bash scripts. We have briefly looked at rebasing on Packer, but we decided that whilst in the long term, it may make maintenance somewhat easier, there are still lots of custom code we'd need to provide for our workflow and infrastructure. It felt like way too much work, for too little benefit. So whilst our code probably isn't as end-user friendly as theirs, I would argue that it's just as effective...

On the downside, our code is targetted for our workflow and our appliances, so is very TurnKey (Debian) specific. It is designed to run on top of our TKLDev appliance (our "build env in a box"). FWIW buildtasks was originally tooled for Ubuntu; but we've long since rebased on Debian. So TBH, I'm not sure of how useful it'd be for you Ubuntu guys...?!

PS sorry for such a slow response... I'm not really sure how/why I missed your post previously...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.