This 'Hitler uses Docker' video seems to be a pretty similar viewpoint on Docker and the world.
Docker in Production: An Update
41–50 of 97 posts
Re: Docker in Production: An Update
#42Earlier quoted context omitted.
Were you using Device Mapper purposefully, or just because you couldn't get a more typical storage driver to work? The general setup instructions recommend either 1. installing linux-image-extra and using AUFS (for kernel versions = 4). Admittedly, the latter strategy is a bit frustrating and counterintuitive on 16.04. When you install Docker it will start automatically and hang because it can't find the AUFS driver…
So you are saying that all default settings are unusable in production, to the point docker might not start at all, and the only cure is series of 5 obscure advanced system setup/configuration that are almost impossible to figure out by oneself and not documented, yet they should be totally obvious to anyone using Docker, right? FYI: It's because of this sort of bullshit that there are articles called "Docker in Prod…
No, that's not what I'm saying. I'm saying that Ubuntu Server 16.04 LTS comes out of the box without AUFS and Device Mapper, and that you either need to enable one or the other before installing Docker or prevent Docker from starting automatically at install time. It sucks, yes, but your description of the problem and its solution is beyond hyperbolic. Googling "docker ubuntu install hang" takes you right to the GitHub issue with the solution at the bottom. And I think it's fixed in Docker 1.13 (it will prefer OverlayFS if AUFS and Device Mapper are not available), although I have not tested it.
Re: Docker in Production: An Update
#43This 'Hitler uses Docker' video seems to be a pretty similar viewpoint on Docker and the world. https://www.youtube.com/watch?v=PivpCKEiQOQ
Don't cry, you can run bash on Windows 10 now!
Re: Docker in Production: An Update
#44> As confirmed by internal sources, they experienced massive troubles to get Docker working in any decent condition I call B.S. on this. Amazon wouldn't have spent so much effort on ECS if this was true.
Has Amazon spent a lot of effort on ECS? I am totally ignorant here, but the people who I consider more knowledgeable about AWS things have said in a nutshell that "in 2015 the things I heard about ECS were not good things, and I have basically not heard any new things since then." Basically stating that ECS was Amazon's attempt to plant a flag in the container-space and that it was half-hearted, not done with the ri…
hey yebyen- i was one of the very first beta users of ECS, and I now work for AWS. first off, sounds like maybe we're not doing the best job we can be with educating users on ECS- that's on us, and we'll focus on improving. to dig into your actual question: when ECS launched, the goal was to do a smaller number of things really well, and then listen to the community on what _they_ wanted to see from a container management platform, and grow accordingly. I've seen a number of significant improvements over the last year or so. Off the top of my head: ECR (thanks @coding123), task placement policies and strategies to give developers more control over how they place tasks and use resources, IAM roles for tasks, event stream for cloudwatch events, service level autoscaling, ALB support, and a number of smaller configuration changes, like multiple network modes, and out-of-the-box support for and awslogs driver. also discovered while writing a workshop the other day that there is a pretty sweet first-run wizard for users just trying out ECS for the first time. in any case, a couple of main takeaways here: i'm seeing a focus on adding features and services that reduce the operational work for developers- let AWS worry about scaling and managing your cluster infrastructure, and you can focus on building cool stuff. beyond that, though, developers have asked for more control, flexibility, and extensibility, and i think ECS is working on delivering that: the cloudwatch event stream can be consumed by other services, the blox open source project (and the already opensourced ecs-agent) let you build custom schedulers/functionality on top of what AWS offers, placement policies let you customize how ECS consumes your cluster resources. would love to know where you get your news and why you haven't heard much about ECS, so we can make sure we fix it. if you want to talk more, you can also DM me
Re: Docker in Production: An Update
#45It's great that hftguy thinks Google Container Engine is stable (I work on it) but I'm sorry to say it's very easy to prove that is, in fact, running Docker on the nodes. You can just SSH into one and see for yourself. Kubernetes was built from the ground up to orchestrate Docker. CoreOS did a lot of work to make it possible to trade rkt in for Docker's engine, and the cri (Container Runtime Interface) is now general…
Is it eventually going to run rkt/cri-o/lmctfy?
Re: Docker in Production: An Update
#46I get the sense that this person wrote a sarcastic, vaguely entertaining piece that drew lots of views. Hoping for lightning to strike twice, they did this again because who doesn't love traffic? That seems to be the entire motivation behind this post, from what I can tell. There's just not a ton of substantiated content here. It's mostly really lousy anecdata like: > Sadly, I am not aware of any serious companies th…
I'm not sure I've personally been able to figure out if it was sarcasm or willful ignorance, but yeah, this article annoyed the pants off me just as much as the first in the series. The fact that it's now worked twice to hit the front page is also a little unsettling, because apparently one of the best ways to reach people on HN now is to just post a bunch of misinformed FUD (with !!Attitude!!) and jump on board the rocket ship!
Re: Docker in Production: An Update
#47the problem is, that the docker (community) or rather the company behind it, focuses on too much, instead of just doing one thing and doing it great. no they need to reimplement the world and create their own kubernetes (or some sort of it). their new website is less accessible as it was in the old version, etc... and all the new projects and people. and the various ways to configure docker. why does a simple contain…
I'd like to see Rkt/Coreos folks start showing how their stuff IS accessible than keep spewing this flamewar crap on HN. I've had nothing but excellent comments from the Kube developers, but every time a Rkt dev or fan comes on here, this is the crap we get.
Re: Docker in Production: An Update
#48> As confirmed by internal sources, they experienced massive troubles to get Docker working in any decent condition I call B.S. on this. Amazon wouldn't have spent so much effort on ECS if this was true.
Has Amazon spent a lot of effort on ECS? I am totally ignorant here, but the people who I consider more knowledgeable about AWS things have said in a nutshell that "in 2015 the things I heard about ECS were not good things, and I have basically not heard any new things since then." Basically stating that ECS was Amazon's attempt to plant a flag in the container-space and that it was half-hearted, not done with the ri…
(AWS employee here)
First of all I can assure you that Amazon is 100% committed to containers. Amazon's compute strategy is aimed at three levels of abstraction: instances, containers, lambda. All three are equally important to Amazon.
With regard to ECS feature set relative to K8, the thing to understand is that AWS follows a startup-like strategy of launching an MVP and then letting customer feedback drive roadmap from there. AWS is definitely not half hearted about ECS. Rather AWS is constantly working with customers to define a roadmap for further development on ECS.
To me the most exciting thing about ECS is the open source work being done around ECS, for Blox (a framework for building out custom container scheduling logic), and the ECS agent itself:
https://github.com/aws/amazon-ecs-agent
With these ECS components you can open issues or even PR's just like any other open source project. Additionally another cool thing we are doing is sharing feature proposals for public comment. You can check out an Amazon employee's public fork of the ECS agent to see a preview of coming roadmap, and we are actively soliciting feedback on proposals such as this one:
https://github.com/aaithal/amazon-ecs-agent/blob/f4d80440db0...
If you have any questions about ECS, feedback, or concerns feel free to reach out to me directly (peckn@amazon.com) and I'd be happy to chat!
Re: Docker in Production: An Update
#49Yikes, I could never work in aerospace.
Re: Docker in Production: An Update
#50It's great that hftguy thinks Google Container Engine is stable (I work on it) but I'm sorry to say it's very easy to prove that is, in fact, running Docker on the nodes. You can just SSH into one and see for yourself. Kubernetes was built from the ground up to orchestrate Docker. CoreOS did a lot of work to make it possible to trade rkt in for Docker's engine, and the cri (Container Runtime Interface) is now general…
So what magic combination of distro + FS do you use to make Docker stable?