- #NOT ENOUGH MEMORY TO START DOCKER DESKTOP FOR MAC#
- #NOT ENOUGH MEMORY TO START DOCKER DESKTOP INSTALL#
- #NOT ENOUGH MEMORY TO START DOCKER DESKTOP PORTABLE#
- #NOT ENOUGH MEMORY TO START DOCKER DESKTOP SOFTWARE#
- #NOT ENOUGH MEMORY TO START DOCKER DESKTOP MAC#
But that tomorrow always comes with a cost. And because of the nature of software, it's easy to build POC's and prototypes that half-work today, with the promise of better functionality and integration in the future. The first objective of a pre-revenue company is to grow as fast as possible and then either get acquired or start generating revenue, which almost always involves marking up their product. I do not understand how in 2022 we still have people hanging out in tech forums like HN that do not understand this.
#NOT ENOUGH MEMORY TO START DOCKER DESKTOP SOFTWARE#
Just telling people to worry about privacy isn't helping, and probably does more harm than good.ĭid you really, truly think that a product like Docker desktop would stay free forever? This is a fundamental aspect of building software products and companies. Privacy advocacy isn't worrying about your privacy, it's understanding how the public, at large, looses access to understanding about where they should share their data. If you care about privacy, limit what software you use, put stuff that you worry about on another machine and keep your damn data off it. Twice.Īll that said, all you people who just shout "privacy, privacy, grumble, grumble, large company, grumble" are a pain in the ass. Of course data would come out of a binary, but which binary are you referring to? The Docker binary, which runs containers and crashed, or the binary that handles the crash of the other binary? Or maybe it's the installer binary that crashed? Mine did. Further evidence of straw man shenanigans is present here in replying to "source?" by saying "the binary".
To be clear, that last part of the straw man isn't a reminder, it's a claim. What info is on these machines that Docker would risk their shareholder value to "steal" or "divulge"? Not much, is the answer. They aren't used by everyone (read the public), and most people that run it (assuming it didn't uninstall itself), run it on their work computer. Sure, Docker runs third party analytics on their site and pixel trackers in their emails. They don't care because most of these customers/users are DOING BUSINESS. People love this because they are Docker customers or long time users. Whatever.ĭocker has personal info on everyone who uses Docker and uses their online services. As most of us get that Docker is nowadays NOT Open Source, the argument falls to "reminding us" that it "uploads a ton of sensitive info" "without consent". I think Docker has produced Open Source code, however. The "reminder" is that Docker isn't free and not "even" Open Source. This is a straw man argument, just in case anyone cares. > Reminder: Docker Desktop is not free software (it's not even source available) and has embedded spyware that uploads a ton of sensitive info from your system without consent when it crashes.
#NOT ENOUGH MEMORY TO START DOCKER DESKTOP PORTABLE#
I also haven't worked with BSD jails or other technologies so I don't know how portable containers are between systems, if at all.
#NOT ENOUGH MEMORY TO START DOCKER DESKTOP MAC#
I don't know what the Mac kernel is missing or what gaps or proposals there are to create a container-like environment. This is approaching the limit of my knowledge.
#NOT ENOUGH MEMORY TO START DOCKER DESKTOP FOR MAC#
This is also why there are different ways to run containers (BSD jails), really what we're talking about is building an isolated environment.Īs far as I know, the Mac kernel doesn't have these same features to create isolated environments, which is likely why Docker for Mac went with a full Linux VM, which includes the kernel. So on Linux, to create a container, you basically use native Linux features to build this isolated environment, and run some process(es) in it.
You can run multiple processes in a namespace (Docker containers can run more than one process!) If you're a process running inside this namespace, to you, it looks like you're the only process on the system. The other feature is "namespaces", aka a "process namespace." It's another feature of the Linux kernel that lets you create an isolated namespace for processes to run in. Whatever runs in here only gets the resources defined by whoever created the cgroup.
#NOT ENOUGH MEMORY TO START DOCKER DESKTOP INSTALL#
(If you install htop for mac, run htop at a terminal, press "t" to go into tree view, and scroll to the top, you'll see kernel_task, the representation of the kernel).Ī "control group" (or "cgroup") is a feature of the Linux kernel that lets you create an environment with a fixed allocation of memory, CPU, and other resources. The "kernel" is the core computer program that interfaces with the hardware. It really hinges on these things called "control groups" and "namespaces," which are features of the Linux kernel.
0 kommentar(er)
