That is true, however jails lose a lot of power without VIMAGE. VIMAGE is not enabled by default yet, and it's pretty unstable (I use it). I really wish VIMAGE would mature, but we're not there yet.
There's also a price for doing it differently. And believe you me, using BSD nowadays is the definition of doing things differently. What for? What I'm getting for losing my time and reinventing the tools that are already available and much more polished?
Dockerfiles can be replicated. Docker Hub can be replicated. Missing things can be compiled from sources, probably. But all that costs time for little to no gain.
FreeBSD might only have a fraction of the community that Linux does, but that's still a pretty large number of developers and sysadmins in real world terms.
Disclosure: I run both FreeBSD and Linux systems.
At the end of the day, both Jails and Docker are well documented. So even the people only interested in blindly copying and pasting commands should be able do the basics.
The real problem FreeBSD and jails face isn't with support nor accessibility but rather dumb prejudice. Much like why many Windows users think Linux is difficult. If you spend your whole time shouting that your way of doing things is the best then you're never going to give anything else a fair chance.
Docker and linux containers in general made things easier and more accessible for many. Switching from that to jails doesn't make sense.
We're not just talking about jails though. The OP was discussing systemd + containers. Switching to FreeBSD to escape systemd isn't that weird of an idea since most of the same Linux software will also run on FreeBSD. In fact I'm seriously considering switching my Debian 7 (Wheezy) servers over to FreeBSD rather than upgrade to Debian 8 (Jessie) and have deal with systemd. Anecdotally I've read other people consider switching away from Linux as well
You might like systemd and Dockers. That's great. But that's your personal preference. You shouldn't be so surprised when other people might prefer to run the same software but on a different platform.
On a tangent note: I also have a bunch of existing systemd systems - RHEL servers, ArchLinux desktops, etc - that I'm very happy with and intend to keep running Linux. I make this point just to emphasise that I'm not anti-Linux nor a FreeBSD fanboy. Just someone who's platform agnostic.
> Sure, then can use both, but why?
Why not? This isn't a sports team where you're expected to only support one product. It's quite possible to use multiple different technologies based on whatever fits a specific purpose better.
Linux/Docker and BSD/jails aren't even in the same league.
Since you don't have any basis for comparison, I'm going to have to assume that you're now just trolling me. So I'll end our correspondence here.
Sometimes, stability is a gain.
... although people like Florian Haas argue that the way that one does things on the BSDs is actually the way that makes sense to do things with Docker, as well, and the way that you think to be "different" is actually the sensible way overall.
* https://plus.google.com/+FlorianHaas/posts/4xjQP1q6DEN
* https://www.hastexo.com/blogs/florian/2016/02/21/containers-...
Since I'm not a Windows fan, I find value in doing it differently, and so have Linux fans. I think you will find FreeBSD and SmartOS users find the cost in time to bring a large enough gain to satisfy their business requirements.
Not today it isn't. Years, maybe decades ago it could be.
What Linux containers do is help to remove the barrier that various distributions introduced, it makes things more accessible and it's more lightweight than using virtualization. Centos, Alpine, Ubuntu, whatever. As long as it is in a container I can work with it. I can even run some Windows binaries with Wine inside a container. rkt is largely compatible with Docker infrastructure, so that too is fine.
But what jimktrains2 suggesting is complete opposite of that, it reduces options.
Personally I'd consider having familiarity with more than one platform would increase one's options.
But ultimately having other solutions on the market is a good thing. Not only because no one solution is the best at every metric (be it stability, security, speed, memory usage, nor any specific requirements), nor because different solutions can appeal to different personalities. But mostly because different solutions might solve a problem in a unique way that the competing solutions may not have considered - often in ways that can ported and thus benefit the competitors and wider community.
So I wouldn't be so quick to dismiss anything that's outside your field of expertise.
I can't afford to learn two technologies that do about the same thing, of which one is significantly less popular, might now have tools that other has and runs on a significantly less popular OS.
Embrace the change, it's for a better future.
Unfortunately, especially when you also factor in the impact of ZFS and DTrace, you are moving into the past, not the future.
Embrace the change of having less security, less control, and less capability to debug your software.
They don't have to embrace the change they have other options. What bothers me is they chose to shoot down everything and anything that has systemd in it out in the public. Just leave the fight and just embrace your choice and allow others to have their choice and don't pee on their parade.
It is in the old rpm vs deb, vim vs emacs, python vs perl dram of the past.