Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Every three months or so I tell myself "right,get your finger out, and do something production quality with containers" and come to the same conclusion this guy did.


My latest foray into bleeding edge ended when I found out AWS Lambda doesn't support python3. :(


Same here. I am trying to use Docker in production since 2014. Production readiness means very different things at different scale. Have you tried LXD? It looks promising.


Have you tried? Make some Dockerfiles, upload to ECR, deploy to an ECS cluster. Hooray, no more dealing with dependency hell and config management.


Actually a single JAR and Ansible deployments solve the same problem as well. The number of times I was running into issues with Docker >>> the number of times I was running into issues with single jars and Ansible. Until this stays like that it is not justified to move to Docker. The business use case is to have a reproducible & reliable infrastructure and not to use containers at all cost.


yeah, I tried....


production quality as in "in production" or as in "something that i will actually use in my day to day"?


production quality as in "I will be happy to run my clients' stacks on this, and won't worry about being woken up in the middle of the night by pagerduty" - I have this right now, and although there are more things I want, the pricetag is too high to justify. I have been doing VM (and container) work since a one of the fist versions of VMWare blew my mind, but given the fact that things work well for me right now, there is no pressing problem to solve. It's a cool way to do things, and I am fully on board with the ideas behind it, but right now it simply doesn't solve any problems I have, and only introduces a ton of new ones.

There is no payback for the hassle...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: