5 ms·
> Sure, your ops team can put together a bunch of stuff manually. And then you can create a bunch of extra stuff that makes it easier for development to handle
by ravenstine 8y ago
> Sure, your ops team can put together a bunch of stuff manually. And then you can create a bunch of extra stuff that makes it easier for development to handle all of that inside virtual machines, and get the network bridging between those apps and the host machine working properly, and all that fun stuff.
I think this is one of the biggest reasons people use Docker, although they tend to forget to mention it since it's not exactly a technical advantage of Docker; in many ways, it allows developers to bypass DevOps or sometimes eliminate them all together. No more creating Jira tickets just to have a specific version of Imagemagick installed on a server.
- bunderbunder 8y agoI think it's one of the two biggest reasons. The other, possibly bigger, reason is that it gives you a way to install fairly complex software and have it reasonably configured and running right out of the box. I use Docker to run stuff like PostgreSQL on my dev box. Not so much because it's a technically superior option (in truth, it's slower and eats more memory than installing it directly on my machine) as much as because it reliably lets me get up and running in a few minutes, just the time it takes to download the image, really. All the other options I've tried invariably require some fiddling, especially if you need an older version. I suspect that all the other codepoints that have ever been spilled on the subject are mostly just an attempt to get ops on board with it. (Disclaimer: All above comments are a mix of wild speculation and Freudian projection. I tend to come down against using it in production.)
- ravenstine 8y agoAt my work, we've had mixed results using it in production. I'd still prefer to using to avoid Ops, but besides that Docker comes with its own bag of issues even though it eliminates versioning conflicts. For development, on the other hand, I absolutely love it. Being able to have different docker-compose.yml files for each of my projects and being able to spin up isolated versions of database services(each with their own volumes!) has been a tremendous win for me.
- jonnycoder 8y agoThis right here. Can confirm, the #1 benefit of using Docker is that 98% of our "Ops" issues has gone away.
- geggam 8y agoNo they haven't. They are lurking around the corner waiting to hit you when you least expect it. The mugging you are about to get is what your ops team has had and are trying to prevent. Enjoy the learnings...
- andrewguenther 8y agoThree years in and this hasn't happened. Our dev team also does ops and we've found that Docker has improved things markedly. But feel free to keep spreading your FUD.
- geggam 8y agoCurious... What is your setup ? AWS ? GCP ? ... managed k8s or you running it ? Outsourcing your operations and pretending the problem is cured by docker is just a bit silly.
- andrewguenther 8y agoDocker on EC2. We had been running bare on EC2 before Docker using a homegrown chroot solution.
- true_tuna 8y agoI’d love for this to be true. Have you had anyone come in and do an audit? I find crazy stuff when I show up at No Ops shops and poke around.
- geggam 8y agoLast year we had a $NAME come for an audit. Well known company and they did not know how to audit inside containers. Still not sure how a corporation who runs RHEL contractually is able to use alpine and ubuntu based containers but it happens. I dont work there anymore and I am glad because when the containers finally do get an audit and the customer is told for X years they havent been in compliance.... well..
- gnufied 8y agoIn default docker installation on most Linux boxes, communication to docker socket itself requires elevated privilege. You can't even do `docker ps`. In jobs I held - people who can pull images and run container on servers, they also could install stuff if they wanted. Is running privileged containers blocked? It just seems something broke down in engineering process, if developers has to bypass admins to install stuff on a server. What happens if that server crashed and burned?
- Spivak 8y agoAccess vs authorization. You can use docker to get yourself local root. If you do it and admins find out you'll be in hot water.
- ezoe 8y agoSeriously. Just to circumbent the silly restriction of system you don't have root on? GNU Hurd was right all along.