4 ms·
If vmware (the company) like money: just let me run containers on bare metal using your management tools. People don't want containers on VMs. They just want c
by nailer 11y ago
If vmware (the company) like money: just let me run containers on bare metal using your management tools.
People don't want containers on VMs. They just want containers. There are many reasons for that.
- peteretep 11y ago> just let me run containers on bare metal I don't think you understand what a container is.
- carlos22 11y agoOh I think he does. You can run linux containers on bare metal - but you loose some features and it's not really secure. Look at SmartOS for example - their zones run on bare metal and provide most of the vm features as well as strong seperation.
- deleted 11y ago[deleted]
- nailer 11y agoEr OK, I'm not sure why you'd think that. Generally on HN we provide supporting arguments. If it wasn't obvious, I'll explain further: Containers run on a shared kernel. That kernel should run on metal, not in a hypervisor.
- peteretep 11y agoIf the containers are running on a shared kernel, they're hardly running on the bare metal. As to "that kernel should run on metal", I hear "Debian" provide such a thing.
- tacone 11y agoIf the containers run on a shared kernel they're effectively running on whatever that kernel runs on, bare metal included. Or not?
- nailer 11y agoYou're trolling. It should be obvious that a kernel is needed to run those containers, and that I was asking for that kernel to be on bare metal. For someone so confident in their technical abilities, I'm surprised you suggest running a general purpose OS as a container parent.
- peteretep 11y agoIf you say one thing, and mean something different, calling someone who points that out to you a troll is odd. I guess by your reasoning you could talk about running your nodejs services "on the bare metal" because it's obvious you need a kernel and nodejs too. I think it might be similarly misleading.
- chris_wot 11y agoYou really aren't helping your argument any here. Linux containers use resource and namespace isolation via the Linux kernel. When we talk about "bare metal", we're using shorthand to talk about the difference between a type 1 and type 2 hypervisor, where when we talk about a type 1 hypervisor we are referring to an operating system that does the actual virtualisation work directly, and when we talk about a type 2 hypervisor we are referring to something like VirtualBox that runs on top of a host OS as a seperate process itself and which does the virtualisation work. Linux containers rely on the operating system via cgroups and namespace isolation to do virtualisation. That's bare-metal under ordinary virtualisation terminology.
- nailer 11y ago"Does your node app run in a VM?" "No, because of the heavy IO load we run it on bare metal" Doesn't sound odd to me.
- peteretep 11y agohttps://www.twitter.com/shit_hn_says/status/234856345579446272 https://www.twitter.com/shit_hn_says/status/2348563455794462... When life imitates art.
- chris_wot 11y agoThe problem is the terminology around "bare-metal". Bare-metal hypervisor are what Popek and Goldberg [1] referred to as the Virtual Machine Monitor (or VMM) - in this case there is a hypervisor operating system and it runs different guests directly. VMWare's vSphere ESXi is a bare-metal hypervisor. The alternative is a Hybrid Virtual Machine (HVV), where you run the hypervisor as a seperate program on a host operating system. VirtualBox is one if the better known examples of a HVV, or type-2 hypervisor. With containers, you could argue that they are actually bare-metal because they share more in common with a type-1 hypervisor, because it is the operating system itself that is creating an efficient and isolated environment within which the application runs. In terms of Linux containers, a combination of resource isolation (cgroups [2]) and namespace isolation [3] achieves operating system level virtualisation. So actually, containers are really bare-metal. 1. http://cs.nyu.edu/courses/fall14/CSCI-GA.3033-010/popek-goldberg.pdf http://cs.nyu.edu/courses/fall14/CSCI-GA.3033-010/popek-gold... 2. https://en.wikipedia.org/wiki/Cgroups https://en.wikipedia.org/wiki/Cgroups 3. https://lwn.net/Articles/531114/ https://lwn.net/Articles/531114/
- quesera 11y agoAgreed. If you're wedded to Linux, check these guys out: https://hyper.sh https://hyper.sh https://news.ycombinator.com/item?id=9622325 https://news.ycombinator.com/item?id=9622325
- pjmlp 11y ago"curl -sSL https://hyper.sh/install https://hyper.sh/install | bash" All those years bashing Windows administrators....
- stephenr 11y agoSo.. you want a dedicated physical server with a single host OS, running your containers... what do you need VMWare for again?
- chris_wot 11y agoTheir management tools.
- stephenr 11y agoManagement of what exactly?
- acdha 11y agoNon-startups have existing applications. It'd be really nice if you could use one tool suite to manage conventional VMs and containers with the same HA & capacity management tools (i.e. keep n instances running on y separate hosts), virtualized networking and storage, etc. Think about working somewhere really big: it's both hard and risky to split a huge business system into containers in one release. Imagine instead doing something like carving out the database, load balancer, task queue workers, etc. piecemeal with a discrete component being containerized in each release. If you were taking the agile approach like that, not saying “Here's a completely different way to manage all of the new services” has significant value.
- stephenr 11y agoContainers and HyperVisors/VMs have intrinsically different abilities and different use-cases. Why would you expect one tool to manage both. Do you also expect your email client to manage your photo library and keep track of your phone calls?
- TallGuyShort 11y ago>> Do you also expect your email client to manage your photo library and keep track of your phone calls? Gmail will basically do that, what with tight integration with Picassa and Google Voice...
- ChrisArgyle 11y agoHypervisors afford many benefits such as dynamic resizing of compute and storage resources, low (or no) impact hardware maintenance thanks to live migration, single-pane-of-glass machine management, etc. Unless your environment is 100% application-level clustered these will be invaluable features.
- yo-code-sucks 11y agoToo bad VMWare's management API's suck a big dick.
- stephenr 11y agoThe vast majority of people who seem to want containers, are those who have embraced the idea that developers can manage servers because they can write (or copy) a Dockerfile and push a container to a container service on AWS or Google Cloud. In those situations you specifically do want containers on VMs because Docker containers do not provide the same level of security and isolation that VMs do.
- scprodigy 11y agoPhoton is built for this case: a minimalist OS to run only as guest. However, check out hyper.sh, the project uses hypervisors to run Docker images, which completely eliminates the need of guest OS, making the whole stack immutable while just offering the hypervisor-level isolation. In my opinion, Hyper is the way to go, instead of the minimalist guest OS distro.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- stock_toaster 11y agoI recall watching a talk (given by @bcantrill I think it was?) where SmartOS had implemented the docker api, but ran the actual "container" via linux emulation, inside a zone. I think they named it "lx branded zones" or something similar. I could see vmware doing something like that -- implementing the docker api, but actually running containers on very lightweight vms, so they can leverage their existing virt infrastructure (memory ballooning, cpu allocation, migration, etc) with it.