These days, to say that Docker adoption has proceeded at a remarkable rate, would be an understatement. There is a lot of Buzz about Docker and it has gained a huge following and a lot of momentum. This is especially true for folks who have come from the Linux world, who have not previously been exposed to the “Magic and Wonder” of native OS containers us Solaris and BSD users have been enjoying for so many years.
When any new technology garners mass appeal, it is imperative from a business perspective to give the people what they want. Joyent has rightly recognized this fact and has integrated Docker support in the most sensible way – which in our opinion is head and shoulders above the way others in the industry have done it. To give Joyent some extra Kudos, their Docker SmartOS integration is really outstanding – albeit currently lacking some documentation detail, which is understandable at this early stage.
Given the choice, we would still always recommend using native SmartOS containers for production services – but do understand there is a very real demand for Docker and that folks either out of choice or necessity have decided to use Docker.
FiFo Docker is now alive!
The Project FiFo team has followed suit and today with little fanfare, we are announcing experimental Docker support with the 0.7.1 FiFo Release. This release introduces a new experimental service endpoint named “Kennel“, that will provide a docker compatible API. The service is far from complete, but it allows for all the basic operations. Anyone interested in FiFo and docker is welcome to try it out, take it for a spin and kick the tires.
We look forward to your feedback, please let us know what can be improved or how you would plan to use the FiFo Docker service in production.
0.7.1 has more then just Docker, as all of our releases it includes a solid list of steady improvements and fixes. Cerberus got a good bit of polish and some aspects missing compared to jingles have been added. There are improvements for the accounting code.
As another new feature we introduce custom resources for Organizations. They allows to limit the number of packages an Organization can claim. This means changing your packages and that has been a tedious and error prone job in the past. To solve this we have added the option to ‘clone’ packages instead of requiring to re-type all the information.
We have added an integration with bugsnag that allows us is to get crash reports of installations and by that further improve the quality. However we hold true to not building a ‘phone home’ application. This is entirely optional and needs to be enabled with an API key. As we strive to make FiFo better and better we would still appreciate if many of you would take part in this program. For those interested please poke one of us on IRC, Twitter or mail and we’ll get back to you with your very own API key.
A full list of changes can be found in the release nots.