Domhnall Currie's picture

Hey guys, is there a 16.0 version of File Server for Docker anywhere?  I can't find it on the Docker Hub and the link from the ? here that points to Docker gets a 400 file not found error when you click on it.  Thanks.

Jeremy Davis's picture

I had issues getting the v16.0 builds working on Docker (FWIW we build our Docker images in a non-standard, somewhat hacky way). I have always intended to circle back and work out the issues. But we're a small team with a ton of stuff to do, so as there has been an apparent lack of interest, I've focused on other things. FWIW v16.0 was initially released ~mid last year and you're the second to ask about Docker builds.

I'm not ruling out getting to it at some point, but TBH, with Debian Bullseye (what we will base the upcoming v17.0 on) now in freeze, I'll need to turn my attention to that sooner rather than later...

If you are familiar with Linux and Docker, then I'd be glad to assist you on how to use TKLDev to build it. If you (or someone) can troubleshoot the issues and get it working, then I'm more than happy to build the whole library to the official TurnKey Docker Hub account.

Domhnall Currie's picture

No worries.  Probably with that little demand, I'd be better off going a different direction.  :)  I understand how the past versions of TK were entire distros running under Docker and not typical "Docker apps" as y'all detailed in the instructions and I've been using Linux probably 20 years, but Docker only about a year so I doubt I'd be able to use TKLDev to build the system.  Even though I often take the "road less travelled" and sometimes do so just for the scenery, if I know that road's going to blow a tire or the bridge is out and I'm going to drive off in the river, I ain't goin' down that road.  :)  Thanks for the quick reply and I appreciate all the effort at TK!

Jeremy Davis's picture

Assuming that you know a bit of bash then you'd be able to use TKLDev no worries I reckon. ;)

Although, I think that fixing the Docker builds will be a case of the devil being in the detail. I don't recall the exact issues I hit but I do vaguely recall a little concern that it may be related to the issue that stops Debian Buster systems running smoothly in a privileged LXC container (there's some issue with the default kernel cgroup config and the version of systemd included). It seems likely that issue will be resolved for Bullseye (upcoming new Debian release) but I'm yet to confirm.

FWIW if my recall is correct, then our current builds may well work "as is" on Podman. In case you aren't aware, Podman is Red Hat's answer to Docker (essentially the same thing; or at least provides a similar "application container" runtime). It's compliant with the Open Container spec and unlike Docker doesn't require a daemon, or need the top process to run as root. So it's potentially a good Docker replacement!? Regardless though, Docker is the one that get's all the attention and currently, outside of Red Hat (and RH based distros) I don't think that it's that easy to install. It won't be long though and I reckon that may possibly change. It will be in the Bullseye repos by default, which will make it an easy install!

Anyway, I'm rambling... Take care and good luck. If you change your mind about having a look at the Docker build (and/or want to use TKLDev to build something yourself), and need any pointers please ask.

Domhnall Currie's picture

I've been using Linux about 20 years, but I've been mostly a GUI guy.  :)  I've used bash enough to say, "What the he** does THAT do?"  LOL  I used MS-DOS from 2.1, though, so a CLI and config files don't bother me.  I looked at Podman a while back and there was some reason I skipped it, but I can't remember why.  Maybe because everything was geared towards RH even though you could get it to work with other distros, and I just didn't feel like climbing that hill.

If I wanted to incorporate more than one TKL appliance into one bundle, TKLDev is the way I'd go?  I checked out the blog entry but haven't had time to dig into the documentation yet.  I've never compiled anything from source before, but I'll give it a crack.  My biggest problem is lack of time, but whatcha gonna do? :)

Jeremy Davis's picture

I've only been using Linux regularly for about 12 years (and exclusively / daily driver for about 8). I started dabbling ~20+ years ago and had to use the CLI a bit to work around issues. I guess though getting involved with TurnKey really levelled up my bash! :)

As for combining appliances, the easiest way to do that would be to use Proxmox and install them as (separate) LXC containers. Although I note that unless you have some suitable spare hardware laying around (an old desktop even perhaps?) then that's a non-trivial suggestion (and you already mentioned on the other thread that you've had issues with Proxmox). Others have used TurnKey on LXD (on Ubuntu) and we did have an LXC appliance of our own. Unfortunately though, there are a ton of issues with running Debian Buster on Debian Buster under LXC. I ran out of time to work on it for v16.x so we've skipped v16.x for the LXC app. We'll try again for v17.x hopefully.

FYI, on Proxmox, you'll either want to run v16.x apps as "unprivileged" or if you really want a privileged container, you'll need to enable "nesting".

Having said that, you could use TKLDev to build a custom appliance that includes multiple components. Whilst it would be possible, it won't be "simple". And it may stretch your bash knowledge (pretty much all the build scripts are bash).

Anyway, good luck with it. If you do have a go at it, please ask if/when you hit any issues and I'll do my best to help out.

Add new comment