You are here
deutrino - Thu, 2021/09/30 - 23:25
Hi there, I'd like to use TKLdev to crank out fresh / customized LXC templates as well as .isos, is this possible? I'm using Proxmox for virtualization so it would be super convenient.
It's hard to find an answer for this question with web search, though I'm sure I may have missed something.
Forum:
hmm, did find this: https:/
hmm, did find this: https://www.turnkeylinux.org/comment/47759#comment-47759
Yep, that's how we do it...
Yep, that's how we do it.
And (in context of your other post) actually, if you don't actually want the ISOs and are creating appliances that are closely based on ours, then another aprroach might actually be to just create your own buildtasks script?! (Instead of tweaking common).
Whilst we use buildtasks to create the various different builds, it leverages TKLpatch (it predates TKLDev and was the only way to public share build code prior to TKLDev). So assuming that you wanted to create a modified Core, you could create your own patch (in buildtasks/patches/custom-patch/) then include it in bt-container. I'd add it just below this line:
E.g. so it would look something like this (note the new line in the middle):
Then create the LXC build of your "patched" custom Core container like this:
Nginx & Redis container?
So it should be "fairly easy" to get TKLDev running, merge the Nginx and Redis container github repos into a new one and build it?
Does anyone know if there's a plan for something like this?
Hi Richard! Welcome to TurnKey :)
No plan at present, but you could certainly build it yourself.
There are 2 ways you could go.
The first is to just start with one of them (i.e. Redis or Nginx) and install the software from the other. This is often the most direct path to getting what you want. Although unless you're familiar with Linux/Debian/etc, it's easier said than done and whilst fine for a "one off", if you want to reuse it later, then it's probably not ideal. I won't cover that any further here, but happy to discuss that at some point if you're interested.
The other option would be the "fairly easy" path you suggest (really easy if you are comfortable with Linux/Debian/bash/git/etc). This post will focus on this path. A high level view of a suggested process would look something like this:
A mid-lever overview of merging the build code would probably go something like this:
Obviously there are lots of details missing from that, but I wanted to give you an overview of what will likely be required. I'm happy to provide more detailed info if/when required.
Thanks Jeremy
Thanks for the detailed post Jeremy. That's pretty much what I was expecting. I might try the first option, but would quite like to have the ancillary stuff like redis-commander in case it's useful. First time using proxmox and containers; feel like a newb all over again.
You're welcome
The other thing you could do is take the easy option and just run both (as separate servers). Sure there's a bit of redundancy, but the LXC overhead is pretty low so you probably won't even notice.
Add new comment