I recently ran into some problems compiling code while building a docker image using a Dockerfile. The compile process wasn’t working, so the failed make install was stopping the container image from being built. There’s 3 ways I could have approached troubleshooting this failed build.
This is the first draft at making a repeatable workflow, I’m looking to get a few more eyes to make sure I’ve captured everything. My next step is getting this into an ansible playbook. Replace the inline IPs with the eth0 IPs of the VMs you build. Hit the link to see the steps and very spare comments:
The one thing I’ve not seen a satisfactory answer to is the scope of a microservice. That is what makes it micro? There’ve been objections to Fowler’s “business capabilities” as still too vague; he’s even written a “sizing” side bar commentary. I’ve heard the “nothing new under the sun” folks claiming that this is folderol that’s been best practice since the dawn of programming.
I’m going to throw my hat in the ring with what may be a blend of the two positions.
If I hadn’t been hearing enough about docker, OSCON was replete with docker. Then I go two days of Dan Walsh on docker. So I think I finally got it. Docker that is.
Now let me be clear, at the $OLDDAYJOB I used Solaris zones to build dev / test environments at a fairly decent scale. So I get containers qua containers, the missing bit was what docker brought to the table. Turning to the internet was less than helpful because docker is in the midst of a massive hype cycle. That, and research on the web is painful.
“Doing research on the Web is like using a library assembled piecemeal by pack rats and vandalized nightly.” – Roger Ebert