Cyberben's picture

I know you all are busy,

I tried to install LXC from scratch on the newest TKCore thinking I could DIY Debian Buster with LXC. I did get the Core running and LXC installed but I realized its behaivior is not the same as the TKLXC appliance.

I will have to learn how to configure a vanilla Debian 10.3 LXC install to work with the TK containers. It will be fun actually figuring that out (TKCore + LXC install configured TK style?) but ....

are you working on a Buster TK-LXC?

Thanks,

Ben

Forum: 
Jeremy Davis's picture

Yes! :) We are certainly intending to produce a v16.0 LXC host appliance. As per all the other v16.x appliances, it will be based on Debian 10.x/Buster.

Having said that, I'm not clear when we'll actually get to working on that. Historically, it has generally been relatively late in the vXX.0 development cycle, although it's also historically tended to be fairly community driven. Long term community powerhouse John Carver (aka Dude4Linux) has been a significant driver of our LXC host in both v14.x and v15.x (and perhaps earlier, although that was before I was intimately involved in the dev cycle).

John has been less active in more recent times but I note that he has been in touch relatively recently. Although I'm not clear how much time and/or effort he will be able to contribute this time around?

Regardless of that, we'd love to hear how you go and if you'd like to assist, you'd be more than welcome. Even just reporting back what works and what doesn't would be useful.

Although if you're interested in learning more about working with TKLDev and appliance build code (as you've already dabbled a bit with getting TurnKey LXC guests working on your Stretch based LXC host). You can follow the links to docs from the TKLDev appliance page, but it's well worth noting that some of the TKLDev docs are a bit out of date.

For entry level TKLDev docs, there is a website page on building an ISO, thought that will only work as seamlessly as that suggests for an appliance that we have already published as v16.x (and even then, for appliances that use upstream source code, not guarantees)! Then there's a slightly more technical overview (on GitHub - within the TKLDev build code repo). Then there's a page specifically for updating/maintaining and applaince.

There are lot more docs there, some which might be useful, some not so much... If you do have a go and have questions and/or hit issues, please ask! Also, if you have suggestions feedback re the docs, I'd love to hear.

Also, whilst the actual appliance is completely different (i.e. Odoo rather than LXC) the discussion in this thread might give some insight into developing/updating an appliance for v16.0?!

Cyberben's picture

Great stuff!

Going to start a project to produce a Turnkey Linux v16.0 LXC host appliance based on Debian 10.x/Buster using the TKLDev appliance build code. 

Talk Soon!

Ben

 

Cyberben's picture

When I get to the build process I get errors after I execute the "make" command.

Check out this image link:

The errors

 

 

Jeremy Davis's picture

The sed command is failing because stunnel.conf doesn't exist in v16.0.

For context, since v14.0, both Webmin & Webshell (aka shellinabox) run behind stunnel. In v14.x/15.x stunnel runs as a single service (configured via stunnel.comf). In v16.0+ Stunnel has 2 separate instances, one each for Webmin and Webshell (named /etc/stunnel/webmin.conf & /etc/stunnel/shellinabox.conf).

Looking at the new and old conf files, the format is the same, so that particular sed line should still wokr as intended, you'd just need to run it against both of those files.

I'm almost certain that you'll hit more issues yet... The error message and the lines preceding it should give insight into what has gone wrong.

Cyberben's picture

I believe it starts here. However I dont understand enough about Stunnel to figure out what needs to happen next.

Jeremy Davis's picture

Is something wrong? Or are you just checking it looks ok?

FWIW the last 7 lines look fine. It just looks like it's running the common conf scripts; the last 4 lines come from the shellinabox script, the very last line in your screenshot comes from this line.

Add new comment