As part of our dockerization efforts we needed some software that was not available in the publicly available alpine linux repositories (such as Consul and Weave) and decided to build our own repository so we would have a standard place to put them. While creating the repository it became clear that the existing documentation was outdated, so I decided I would document the steps needed to get a repository set up for Alpine Linux.
I just got back from the Container Camp conference here San Francisco. It was an informative conference with presentations covering a wide range of interesting topics in the containerization ecosystem. There was a lot of discussion about the Docker application suite since they are the dominant player, but there was also good coverage of alternative approaches and presentations on the full spectrum of tooling required to use containers in production.
I recently had the opportunity to show the world what it is like to be part of Funding Circle’s engineering team in the London office.
Containers are at once both simple and difficult to grok. One lunchtime, while trying to understand the internals of docker, I accidentally created a container standard which must never, ever see the light of production. I called it Navvy.
Service oriented architectures can have many benefits, but there are trade-offs as well. One immediate annoyance is setting up multiple applications to do local development.