One good thing with the name is it’s highly searchable.
Count your blessings that it’s not jailctl. I’m sick of nounctl as the name for every tool.
Fair linguistic point. Hopefully, it should be simple to make an alias to invoke the janitor (or dungeon_master?) by whatever name you prefer.
But avoid the ‘spawn’ proposals: @Jip-Hop admitted in the GitHub discussion that he would prefer lxc over systemd-nspawn and picked the latter because it was already available. If jailmaker is to have an official future, I would not exclude a switch to a different daemon.
Is Minotaur too derogatory?
So where does iXsystems stand in all of this? Surely they’re not going to casually just go with a third-party solution without absorbing the code and development in-house?
If “Linux containers” will eventually be an official feature for SCALE, it should be developed/maintained by iX. If they want to use systemd-nspawn instead of LXC (for whatever reasons), then it should be so.
Why do you assume this? There’s plenty of third-party code they use.
Without their own in-house development, for an officially supported TrueNAS feature?
I can’t imagine such a scenario like this:
"We’re proud to announce the release of TrueNAS SCALE Mullet!
Disclaimer: All of your “Linux containers”, which you created and managed with our official GUI menu, will have to be re-created and re-configured because the developer of the project switched the technology for its backend."
Warden called, wanted to ask you where you’ve been these past few years.
“Sandboxes” are not (yet?) an official feature of SCALE. Maybe in Flounder or Halibut… (My proposals, which may fall flat of the actual fishes.)
But if iXsystems takes the project on-board, I can imagine that there will be discussions whether to keep it as it accidentally grew out of what-was-there or to switch it to LXC, which is apparently the more secure and enterprise-friendly alternative, and incidentally side-steps systemd and its haters.
Were you there last month, when iX pulled the rug under the feet of their old forum, with one week notice and a switch date of April Fool Day?
That’s already happened with Gluster.
:groan:
I’m not iXsystems, but goodness that hurts… ![]()
Ouch. ![]()
Points taken. Points taken…
That was actually this month; it was announced 1 Apr and effective 5 Apr.
I can understand the confusion. I thought it did as well (I’m still reading everything and trying to prep myself for my build next week). See Compare TrueNAS Editions - Powerful Storage Platform
It says quite categorically that it supports Docker. For me, personally, I don’t care, I don’t plan to use Docker and have never used Docker, but to give them some credit it does say it does!
“Can run Docker containers” is not the same thing as “includes the Docker software.” There are a number of container managers that can run Docker containers but are not Docker. But agreed that they could be more clear about this. Though it doesn’t change the fact that the poster in question parachuted into this thread while clearly knowing nothing about TrueNAS.
Definitely could be clearer! I took it to mean it includes Docker, which I just went “meh” and moved on to the next bit as I wasn’t fussed. There are lots of things that do excite me, the idea of easily being able to backup critical stuff to an S3 service like Backblaze really does interest me and fits a gap that has me fretting. I’ve always felt my backups have never been enough since the days that QIC ceased to be practical.
FYI this behavior seems to have worked its self out after a few days. No longer having delays
Update went completely smooth and unspectacular. Sorry for being late to the party, but I missed anyone giving a heads up to users of TrueCharts.
If you run TrueCharts apps you must follow this procedure after upgrading to Dragonfish!
I didnt know about this beforehand unfortunately. As of now, all my Truecharts apps work just fine post dragonfish upgrade. Are they just going to suddenly stop working properly if I do not do the linked procedure? Would a simple uninstall/reinstall from scratch suffice?
I believe there was previously a note on the migration guide that your apps would continue to work, but I don’t see it there now. Since the migration procedure seems to be a semi-automated way to reinstall the apps, I’d expect manual reinstallation to work as well, but you’d want to follow their instructions to set up the OpenEBS app first.
