<img style="border: none; background:none; width: 0; height: 0;" src="https://share.polymail.io/v2/z/a/NThmOWQ5YWRiNjU4/RVUZWb1MeG6gwq5nKxIQSKC5Yxtv6khUBafG15YKcoq05pj8hytNtTyrZo4oJ0-BxSz3KjnSnJlKpqL98Ap_y2lfQUB6E48g-sBYtFSSb9Y8o5LNPMh99pPgfgFEVDAQbeGCi2Zx1eBjPOKB1sn4_w-ayw==.png" alt="" width="0px" height="0px" border="0" /><div></div>
<div></div>
<div></div>
<div>
Hi all,</div>
<div><br></div>
<div>Just to address your original message Matt - I’ve been using containers/Docker myself for 3+ years and in my current workplace (Moneyhub) we’ve been using containers in prod for over 2 years now. Has it made things easier? Definitely. We no longer have to worry about any state across vms or physical machines. We know that if it has a container runtime (Docker) on it, then we can deploy to it. It’s allowed us to give up using configuration management tools, which I’ve always found to be fickle beasts when they go wrong! But there’s definitely a cost. The barrier to entry is higher. Docker is a pretty unreliable product, every minor release tends to break something critical. And like you said, managing persistent storage is still a problem.</div>
<div><br></div>
<div>I don’t see what the problem with using containers in prod is though - Google have been doing it for nearly 10 years now. So have many others. So as a concept its obviously battle tested!</div>
<div><br></div>
<div>I agree with you on rkt though. It’s a much simpler proposition, far more unix like. Not like Docker with its client/server, ever changing api between the two, and not knowing which process is actually running your container. We’re hoping to have moved all of our containers to rkt soon!</div>
<div><br></div>
<div>My suggestion to anyone looking into this stuff though is go and look at the OCI (<a href="https://www.opencontainers.org/">https://www.opencontainers.org/</a>) and the Kubernetes API’s. As much as Docker don’t want to admit it, these are going to be the standards that everyone adopts in the container world.</div>
<div><br></div>
<div id="psignature">
<div>James</div>
<div><br></div>
<div>Ps. I think this is my first time posting on this list - so Hi everyone!</div>
<div><br></div>
<div style="font-size:10px; color: #7E8F9F;">Sent from <a href="https://polymail.io/" target="_blank">Polymail</a>
</div>
</div>
<br>
<br><div class="gmail_extra"><br><div class="gmail_quote"><div dir="ltr">On Fri, 21 Apr 2017 at 10:53 Matt Willsher via Swlug <swlug@mailman.lug.org.uk> <<a href="mailto:Matt Willsher via Swlug <swlug@mailman.lug.org.uk>">Matt Willsher via Swlug <swlug@mailman.lug.org.uk></a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><!DOCTYPE html><html><head><meta name="viewport" content="width=device-width"><style>a, pre, code, a:link, body { word-wrap: break-word !important; }</style>
</head><body>Thanks for the feedback guys.<div class=""><br class=""></div>
<div class="">David - when you say in hindsight you chose the wrong technology with LXC, what do you mean?</div>
<div class=""><br class=""></div>
<div class="">My reasons for the original questions are that, in looking for a new role, I’m finding Docker mentioned a lot and it gives me some pause. I don’t actually think there is a lot wrong with the 'traditional’ packaging apps into an OS native format, using config management to set up a VM and deploy into that. I can see the theoretical benefits of Docker, but the extra overhead and complexity, security and storage matters seem like a time sink. </div>
<div class=""><br class=""></div>
<div class="">I’ve dabbled with Docker in dev situations and built up a reasonably complex compose file that set up some home media components. I can see the appeal for large-scale environments where components need to be regularly updated as part of a scheduled release cycle, but issues around patching of the base containers and general workflow seemed rather nebulous. Abstracting away the underlying platform is appealing - all that’s needed in the runtime environment is a stock Docker OS (CoreOS, Atomic or Ubuntu seem the best candidates at the moment, but ), though the announcement of Dockers base OS is an interesting one.</div>
<div class=""><br class=""></div>
<div class="">I wonder if rkt will ultimately be the tooling of choice outside dev - it does away with the union filesystem, is more aligned to Kubernetes terminology, leverages other projects rather been an entirely self-contained eco-system as Docker is becoming. Though of course, they’ll recommend you run it on CoreOS :)</div>
<div class=""><br class=""></div>
<div class="">I think <a href="https://thehftguy.com/2017/02/23/docker-in-production-an-update/" class="">https://thehftguy.com/2017/02/23/docker-in-production-an-update/</a> and the comments there after raise a lot of good points.</div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class="">Matt</div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class="">
<br class=""><div><blockquote type="cite" class=""><p>_______________________________________________<br>Swlug mailing list<br><a href="mailto:Swlug@mailman.lug.org.uk">Swlug@mailman.lug.org.uk</a><br><a href="https://mailman.lug.org.uk/mailman/listinfo/swlug">https://mailman.lug.org.uk/mailman/listinfo/swlug</a><br></p></blockquote></div>
</div>
</body></html><div class="gmail_extra"><div class="">On 20 Apr 2017, at 10:27, David Goodwin via Swlug <<a href="mailto:swlug@mailman.lug.org.uk" class="">swlug@mailman.lug.org.uk</a>> wrote:</div><div class=""><div class=""><br class="">At $job-1 I built a hosting platform for (mostly) wordpress sites using LXC containers (with hindsight I chose the wrong technology - but at the time LXC seemed more mature with support for e.g. privilege separation).<br class=""><br class="">I think it's hosting about 2500 sites now - spread over about 20 VMs.<br class=""><br class="">So - they are "production ready".<br class=""><br class=""><br class="">But it does depend on the application(s). Deploying something like a standalone Wordpress site (minimal interdependencies) is quite different from a large bespoke application.<br class=""><br class=""><br class="">Container management/orchestration is still something that's being worked on. Kubernetes looks very promising.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Do you use it and if so to what degree? Has it made your liked easier?<br class=""></blockquote><br class=""><br class="">Using it - Yes. But not entirely.<br class=""><br class="">I makes it easier to deploy the application to live - as there's no "build a VM, install stuff onto it" stage...<br class=""><br class=""><br class="">David.<br class=""><br class="">_______________________________________________<br class="">Swlug mailing list<br class=""><a href="mailto:Swlug@mailman.lug.org.uk" class="">Swlug@mailman.lug.org.uk</a><br class="">https://mailman.lug.org.uk/mailman/listinfo/swlug<br class=""></div></div></blockquote></div><br class=""></div></body></html></div></blockquote></div><br></div>