4 ms·
> It's the same with Docker on Windows And the same with Docker Desktop on Linux: https://docs.docker.com/desktop/install/linux-install/ https://docs.docker.co
by jolux 4y ago
> It's the same with Docker on Windows
And the same with Docker Desktop on Linux: https://docs.docker.com/desktop/install/linux-install/ https://docs.docker.com/desktop/install/linux-install/
- pxc 4y agoThis strikes me as such an obviously stupid, self-defeating design that I have to be missing something. Why would the Docker developers do this? Did doing it locally not work well? Is all that just to 'spare' Linux developers from actually installing Docker on their machines?
- sdf4j 4y agoMaybe you want to run a completely different kernel, or distro, from your prod environment.
- yamtaddle 4y agoThe trouble with Linux is that anything you don't vendor in will be a giant fucking headache when it comes to support. But then, so will anything you do vendor in, as soon as some shared lib your vendored-in dep relies on is at the wrong version, or when it encounters some oddball config/package combo, or whatever. Here they appear to have chosen to vendor in the whole damn OS, which, given the realities of supporting Linux, doesn't seem totally insane to me. I'd expect it also lets you run it with reduced permissions (not everyone has root on their workstation) and to generally make cross-distro operation much more reliable and consistent.