The issue is that the Gluu Server is not one application, but the integration of several services: oxAuth, oxTrust, LDAP, HTTP. There are also file system resources, like certificates and keystores, that get generated. So dockerizing the Gluu Server is easier said then done. Each services needs to be containerized, and there is orchestration required.
Ideally, we'd like to maintain a similar ease of use with a docker distribution as compared with our chroot package distribution. From a commercial support perspective, we're concerned about what happens when a customer calls with an urgent production problem--will we have the expertise to help them. And will we be supporting docker, or the Gluu Server?
As a first step to supporting docker, we've been collaborating with [Containership](http://containership.io). We developed docker containers for OAuth (no SAML yet...), and we will soon announce availability of the Gluu Server in their marketplace. For customers who want to deploy a cluster of Gluu Servers on public network IAAS providers (amazon, azure, digital ocean, etc), this will be an interesting option. We also like that Containership's staff can help support docker, and Gluu can focus on supporting our application.
In the future, we may start releasing more information on how to use the container versions of the Gluu Server components using your own orchestration tools. This will probably happen in the next six months or so.
But for right now, we're still recommending using the chroot linux package.
If you're in a rush for a dockerized distribution, the only way to get it is to engage us for professional services.