One of the changes I made in the recent Milestone 20 update was to split out the release packages to give more flexibility.
Thiis allowed me to release a micro update to Milestone 20 (imaginatively called m20.1 or update 1), which updates the illumos bits but shares the same main package repository as the main Milestone 20 release.
And the other thing I can now do is build variant releases. So Tribblix has an LX variant!
You can download the omnitribblix ISO image from the Tribblix download page. It installs, operates, and is packaged just like regular Tribblix. If you don't use LX zones, you probably wouldn't notice the difference.
(It's versioned as m20lx.1 - the update 1 there means that it's a parallel release to the regular Tribblix Milestone 20 update 1.)
You can also update to the LX variant from either the regular Milestone 20 or Milestone 20 update 1 releases, in the normal way. It's a micro update, or sidegrade perhaps, but uses the same upgrade process as regular upgrades.
And, because of the magic of boot environments, if there's a problem you can roll back.
Anyway, once you have omnitribblix installed, how do you create an LX zone? Very easily, in the same way you create and destroy other zones on Tribblix, using the zap utility.
Before you can do that, though, you need a Linux image of some sort to install.
I've been using the same images I use under Docker. So, for example, if I want Alpine then I would go:
docker run alpine uname -a
and then get the name of the container
docker ps -a
and then export that with
docker export romantic_galileo > alpine.tar
Then copy the alpine.tar file to your omnitribblix system. If you want something a bit richer, then Ubuntu will work. But generally exporting a Docker container like this will work, and the image characteristics will be a good fit for a zone.
And then all you do to create the zone is use zap, specifying that it's an lx brand and telling it where the tarball is:
zap create-zone -z alpine -t lx \
-x 10.0.2.99 -I /tmp/alpine.tar
and just zlogin to it as normal.
There are constraints around networking - you have to be exclusive-ip (the -x flag) and zap will create (and destroy) the vnic for you automatically. But the networking in the zone won't actually be configured. (While you specify the IP address in the command, that just tells zap how to configure the network plumbing and the vnic.) You'll have to log in to the zone and use the native tools to identify and configure the network, like so:
/native/sbin/ifconfig znic0 inet 10.0.2.99 up
/native/usr/sbin/route add net default 10.0.2.2
And off you go. Sitting on an illumos box with all its goodness, with access to the wide variety of the Linux ecosystem at your fingertips.