chrislaco
I know a few folks who were on metformin long term for diabetes related things, and after the switch, lost a TON of weight from metabolic changes in just that year compared the entire past.
As with both generally, they're starting to clamp down on prescribing/filling for non-diabetic folks (aka, people using it just for weight and not clinical diabetes itself).
And many folks don't, because the amount of unreadability from having to concat 20 statements in a && fashion to cut down layer size gets out of hand. This leads to folks then having to use scripts to clean the layers, which leads to reuse in things like Packer, which leads to even more problems when the base image changes culturally.
I'd also argue the that it's a matter of familiarity. Every time we change the base image culturally, we have to retool for a different method of making the things in it (apt/dnf/yum -> apk), so while large distro images are bad, they're familiar and predictable (with a mature package set and releases) to what we're used to doing on servers.
Or folks use another tool to abstract that (like Ansible or Chef), which brings us right back to not using Dockerfile.
vxlan (overlay) and bridge, depending:
"Docker ships with 2 drivers:
bridge -- This driver provides the same sort of networking via veth bridge devices that prior versions of docker use, it is the default. overlay -- Not to be confused with the "overlay" storage driver (thanks overlayfs), this driver provides native multi-host networking for docker clusters. When using swarm, this is the default driver."
Personally, I suspect that the Intel drivers for the Iris chipset took a crap in 10.10 compared to 10.9.
RHEL used to be notorious for breaking their Perl 5 dists. The first rule of Perl was to compile your own the server.
I'm guessing something less sinister, like a missed https:// in a link somewhere.
However, when you get a bundle install conflict error about json, one gem needing a higher version, and one needing a lower version... adding json to _my_ Gemfile/gemspec to fix it when I'm not using json directly is also not the right answer. Sometimes, even that doesn't work at all.
That's a shame, because bundler is a fail. Ok, anger aside, if I had a $ for every time json has been a dep resolution blocker on bundle install, or chef, or net-ssh, Id be rich.