Live data from Hacker News

Run More Stuff in Docker

jonathan.bergknoff.com

151–160 of 293 posts

Re: Run More Stuff in Docker

#151

Docker is intimately tied to Linux. It it only "cross platform" in that it can use a VM (Mac, WSL2) or flaky compat layers (FreeBSD). If software embraces Docker, it effectively excludes other OSes, like Windows, BSDs, Haiku, Fuschia, etc.

> Docker is intimately tied to Linux.

Linux and windows:

https://hub.docker.com/_/microsoft-windows

Re: Run More Stuff in Docker

#152

Let's not. I don't want to install Chrome which is already 73 MB, now bloated up with a whole lotta bullshit that's 500 MB+ image. Imagine downloading every application as a docker container. WTF. Docker is for distribution of applications when deploying them to servers. As a developer, it's amazing at that and have brought peace and joy in devops. Let's leave it there, shall we?

I disagree.

I think the beauty of docker - and this should spread elsewhere - is that everything starts with one text file.

The crufty part is all the crap that has to be added to the docker run commandline.

Re: Run More Stuff in Docker

#153

Earlier quoted context omitted.

What? Why would it prompt this? Docker supports SELinux.

I don't know the specific issue, but RH's been trying to push Podman fairly hard...

Fedora is using cgroups v2 by default since last year. This version of cgroups was not supported by docker until a couple of weeks ago. So as a Fedora user you could either use podman or modify your installation to use cgroups v1 instead.

Re: Run More Stuff in Docker

#154

Earlier quoted context omitted.

> Imagine downloading every application as a docker container. WTF. Help me understand the WTF here, and also how that’s meaningfully different from an OS X app?

A MacOS App is just what you need to run the app on MacOS. A Docker Image is essentially a mini operating system in a can. Most Docker images contain shells, the entire Python install, an init sequence... piles and piles of redundant stuff. If you are running a Docker image on MacOS or Windows, you first have to start docker which is itself a Linux Virtual machine. Docker is a great dev tool, but if you don't need it…

I think you are responding too literally to his comment, which is spot on.

A macos app is running in a sandbox and runs in a conceptually similar way to docker.

Go look in ~/Library/Containers

also look at the filesystem under .app

Re: Run More Stuff in Docker

#155
post #148

Earlier quoted context omitted.

> If you’re running Docker, you’re running Linux As slow as it is some people apparently enjoy running docker from win / mac

Docker needs Linux to work. On Mac/Windows containers run in a Linux virtual machine.

I thought so too, but apparently support for native Windows containers has existed for a while now. e.g. https://poweruser.blog/lightweight-windows-containers-using-...

Re: Run More Stuff in Docker

#156
post #7

Docker is the NoSQL of 2020.

Not really. Containerization has clear and obvious advantages over the traditional bare-metal approach.

For security purposes as used since the early days in mainframes and big iron UNIX, surely.

As workaround for broken dependency management, not really.

Re: Run More Stuff in Docker

#158
post #110
post #100

Earlier quoted context omitted.

I am so glad I can read something like this in public. When I say stuff like this in job interviews, I get eye rolls and don't end up getting a job. The industry is so far up its ass lately, no one even dare stating the facts in public. /rant

Now talk about deploying something NOT using Kubernetes. The double whammy. Now you're looking like an insane 100 year old graybeard fossil.

Fossil here, happily using VMs.

Re: Run More Stuff in Docker

#159

For end user devices, I much prefer Nix/NixOS [1] for this kind of thing. With Flakes [2] (experimental feature), you get full reproducibility. The documentation is spotty and there is a considerable learning curve, but I've switched to NixOS on my laptop and desktop early this year and am mostly very happy with it. That doesn't cover sandboxing though. I would actually agree that sandboxing / restricting application…

I've examined this a number of times over the years for deploying a ROS (Robot Operating System) workspace to robots and laptops. Some of our competitors use snaps or various container technologies for this, but I've always felt that the isolation/sandboxing would be more of a barrier than a help— it's one more layer of udev rules and other indirection to have to punch through with another set of config files (and to…

apt/.deb unfortunately has a much much higher barrier to entry.

Docker, is simple enough to get even the most inexperienced developer going in a very short time.

Re: Run More Stuff in Docker

#160

Earlier quoted context omitted.

wtf are you doing to create such large Docker containers? Are you installing each app on top of a fully-fledged Ubuntu? Are you leaving the build tools in the final container?

If you're building docker images FROM SCRATCH then there's no improvement over a zip file or statically-linked single binary (which is what packages and installers already use). Meanwhile Docker adds many more restrictions and limitations and is not a good fit for consumer-focused interactive GUI applications which are not the web and console apps that work best with Docker.

One improvement is the container is sandboxed and dependencies to the host must be added explicitly, eg --volume, --env, --net.

Sure you could do the same with chroot manually and there are many other tools that does the same thing, but somehow the docker way of representing these concepts are more graspable for average user, and much more widespread use.

Post reply on HN