The problem i have with cubernetes is the following: I as a small developer and small server owner don't have the ressources to even get started. The first thing i see at cubernetes is a cluster. Why a cluster. Do i need to cluster my Raspberry pi's to get something out of it? Do i need to buy 3 servers just to run 5 containers? In docker its easy. Download Docker. Start container. Install container manager like plat…
> as a small developer Do you need kubernetes? I know the hype cycle is mad for copying big tech, but if stackoverflow can operate on a couple of IIS instances I’d argue that you almost never need kubernetes.
Why doesn’t anyone weep for Docker?
191–200 of 248 posts
Re: Why doesn’t anyone weep for Docker?
#192The first and only experience I had with Docker as a company was requiring me to sign up to download their mac osx client. They seem to have since changed that policy but it really made me resent them, and made them feel pretty unfriendly.
Re: Why doesn’t anyone weep for Docker?
#193Earlier quoted context omitted.
Sure. None of the things you mentioned are DevOps. DevOps is two things: 1. Applying the methods of modern software development (version control, automation, DSLs...) to operations (provisioning, config, deployment, monitoring, backups...). 2. Reducing silo barriers between devs and ops groups so that everyone is working together as a team, rather than blaming each other for poor communication and the resulting messe…
Just some minor clarifications: - DevOps is a peer with Agile and Lean. Scrum and XP are Agile implementations. Scrum doesn't prescribe ways to code, XP does. - 90% of what people develop or run today should be in containers, and not because containers are great, but because of the DevOps patterns of IaC, immutability, reproducibility, homogeneous environments. Whether you run them on your laptop, a VPC, AWS Fargate,…
Sorry but no. Container is __a__ way of achieving a small part of what you are talking about but not the only way.
Break it down:
- IaC: how do you containerise a load balancer? Terraform gives you infrastructure as code without containers.
- immutability: VMs, AMIs are immutable just like containers are (discounting the entropy that happens in every OS)
- reproducibility: Same, VMs, AMI, Terraform, Ansible all give your that
- homogeneous environments: Not sure what you mean by that, your Cisco or Juniper firewalls are not running in Docker so I am pretty sure you already have "heterogenous" environment if you meant that by what you wrote
I absolutely disagree this approach that we need containers for the reasons you just mentioned.
Re: Why doesn’t anyone weep for Docker?
#194Earlier quoted context omitted.
Kubernetes seems to be intended for large, complex environments but yours seems to not meet that category. What have you gained by using it?
(Not OP) I'm running a single node kubernetes cluster because it provides much needed isolation between services as well as, and that's the biggest part, a aingle and simple way to have everything in one place. I can duplicate a service I'm running 1:1 with a new version for testing in 2 minutes, I can tear it down in 2 seconds. I can roll back changes in one command, I can wipe the server and reinstall everything fr…
Re: Why doesn’t anyone weep for Docker?
#195Maybe this isn't quite the perspective the article's taking—but damn near no one visibly wept for LXC when Docker stomped all over it in terms of “what people think containers just Are”. And now the news asks why I don't weep for them? Live by the stomp, die by the stomp.
I weep for Solaris Zones and FreeBSD Jails. Granted I don't really have much experience of them, I do have some experience of containers on Linux via Docker but also in constructing a minimal container runtime in C (not OCI compatible or anything), but my point is there was a lot of work in this area before Docker and especially in the case of Zones, freely available today in illumos distributions, are completely ove…
Re: Why doesn’t anyone weep for Docker?
#196Earlier quoted context omitted.
It would surprise me if Linus even knew about Solaris when he worked on the first release of Linux. Solaris’ first release was in June 1992, with first use of the name in marketing materials in September 1991 ( https://en.wikipedia.org/wiki/Solaris_(operating_system)#His... ) Linus’ famous message was from the same time (September 17, 1991) Calling Linux an open source version of Minix is more appropriate, but it sti…
I think that, once you're going that far back in history, it's pretty critical to keep track of the GNU/Linux distinction. Linus just wrote a kernel. And then the GNU userland, which had already been in development since the mid 80s, but was still somewhat lacking a workable kernel, was adopted as the official userland to use with the Linux kernel. And at roughly the same time, IIRC, when Sun decided to migrate their…
Re: Why doesn’t anyone weep for Docker?
#197Can anyone offer a good guide to DevOps for people who don't directly use these tools but work with engineers who do and would like to learn more? The whole ecosystem of servers, cloud infrastructure (and all of the different offerings there), Docker, Kubernetes, CICD tools etc is a bit overwhelming to get into.
What most enterprises think is DevOps is different from what dsr_ wrote. They have admins that maintain their pool of servers. They have developers that are fluent in the stack of their application. They decide they need to have some of that cloud, containers, CI/CD stuff. Turns out they need people who can write code that builds their programs, tests their programs, packages their programs, provisions cloud infrastr…
You mean the companies we regularly fail every aspect of engineering?
dsr_ summed up pretty well how Amazon and a bunch of companies think abut DevOps. Coincidentally these companies produce the highest grade of software, tools, services etc.
>> Most of their admins say they are not programmers, so it's not their job.
What you are describing is the 90s approach to IT. These companies disappear really fast. IT is changing just like agriculture was changing long time ago. Toffler talks about this in The Third Wave.
Old approach: lets do everything by hand New approach: automate most of the things you can
>> In an unjust world, you end up with three silos. Programmers say their code compiles on their machine, admins say they have installed the new server, devops frantically try to build some pipeline that deploys that code on that server.
I migrated countless companies from 90s approach to CI/CD world, they never looked back. You just think that because there are late adopters this world is going to exist indefinitely. I do not think so.
Re: Why doesn’t anyone weep for Docker?
#198Earlier quoted context omitted.
Why would you be allowing devs to directly deploy to production in a company with 30,000 developers? Surely you'd have proper release management where Ops teams would review deployment artifacts before deploying them?
You wouldn’t but you wouldn’t give every dev root access to every dev box either... would you?
In any case the notion of "the root password" seems weird, root passwords should be unique (even for VMs), randomly generated, and mostly not used; in most situations you'd use publickey authentication instead of passwords.
Re: Why doesn’t anyone weep for Docker?
#199Earlier quoted context omitted.
> as a small developer Do you need kubernetes? I know the hype cycle is mad for copying big tech, but if stackoverflow can operate on a couple of IIS instances I’d argue that you almost never need kubernetes.
I don't need Kubernetes, no. But what do I use? What's there to automatically deploy my software when I push in a simple and reliable way? All the other stuff I can do myself, but I want something to deploy stuff to servers.
Re: Why doesn’t anyone weep for Docker?
#200Earlier quoted context omitted.
I don't need Kubernetes, no. But what do I use? What's there to automatically deploy my software when I push in a simple and reliable way? All the other stuff I can do myself, but I want something to deploy stuff to servers.
"git checkout X && git pull" ?