We have Docker deployed just about everywhere in production. The only places that we don't use it are our haproxy looad balancers that terminate SSL connections and route requests. The setup on those is already simple so we didn't feel the need to containerize it. But everything else is, and we've found it a revolutionary upgrade in the manageability of our environment. And yet... I find the notion of Dockercon odd. I don't feel like I need rediscon, or haproxycon. Docker is a great tool, and maybe we'd get some benefit from attending a conference on it, but for us it's just not quite that big a deal. It makes a lot of things easier, but the main benefit of that is we can focus on the things that are a big deal, i.e. business goals.
"All the people use docker in testing environments."<p>Not really true, there were a few who said they were running Docker in Prod, but yes, the majority was not production-ready just yet
my employer was kind enough to send me and while I enjoyed most of it I'm sorry but I feel the urge to nitpick:<p>> the organization was perfect<p>was really not considering this wasn't a free event/meetup and had plenty of big sponsors.<p>Sessions got delayed by 10/15/20 even 30 minutes continuously, including the opening and closing keynotes on day 1 and 2 (!!). On day 2 it was <i>very</i> disappointing to show up on time in the morning and being prevented from even entering the room because all of a sudden the keynote was going to start 30 minutes late (which was really more like 40).<p>The main room had a ridiculous single file entrance/exit, food was ok on day 1 but disappointing on day 2 (little sandwiches). Lots of noise coming from regular visitor to the museum and even from people just walking past the venue since the main room had glass walls directly to the outside.<p>Also having day 2 on a national holiday with lots of families visiting the museum wasn't a great idea re noise.<p>As I mentioned: I'm nitpicking but it had to be said