Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Run More Stuff in Docker

jonathan.bergknoff.com

Post reply on HN
Print view View original

51–60 of 293 posts

Re: Run More Stuff in Docker

#51

Post by ris »

stack_underflow wrote: post #35
setheron wrote: post #19

Earlier quoted context omitted.

Reach out to me if you want to learn Nix I'm always happy to help people climb the steep learning curve

Curious, does one need to use nixOS for an optimal experience? I've been using debian for a long time and would prefer not to have to switch OSs but the idea of using nix for having full control over my package graph is very tempting. I've been somewhat procrastinating on trying nix as I've heard GNU Guix has a similar feature set and haven't been able to decide on which one to dive into... My ideal setup would be to…

> Curious, does one need to use nixOS for an optimal experience?

My experience: no. I've been very happily using Nix on debian for years. Debian gives me my boring desktop apps (I have very very boring tastes), almost all my tinkering and development starts with drawing all the prerequisites from Nix.

The only times you get weirdness from using non-NixOS linux are things like running opengl apps, which simply require a wrapper script like `nixGL` to function properly.

And darwin Nix is just about the only thing that makes macos a bearable platform for me.

Re: Run More Stuff in Docker

#52

Post by systemvoltage »

peteretep wrote: post #50
systemvoltage wrote: post #49

Earlier quoted context omitted.

Jumping from 73 MB -----> 500 MB or whatever. Have you been running Docker on your system? Have you tried running: `docker system prune -a`? It's gonna print something like Total reclaimed space: 31.2GB .

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?

That's what I am trying to ask myself too! I am sorry that I am a developer and I need to run a bunch of docker compose files.

Re: Run More Stuff in Docker

#53

Post by joshuanapoli »

peteretep wrote: post #46
systemvoltage wrote: post #42

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?

> 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?

Loading a 1GB image to run a 50MB executable can be trouble. I used to work while commuting on a train on a daily basis. Unexpectedly needing a big download could ruin my morning.

Re: Run More Stuff in Docker

#54

Post by peteretep »

joshuanapoli wrote: post #53
peteretep wrote: post #46

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?

Loading a 1GB image to run a 50MB executable can be trouble. I used to work while commuting on a train on a daily basis. Unexpectedly needing a big download could ruin my morning.

Why are you running such huge images for a 50MB executable?

Re: Run More Stuff in Docker

#55

Post by cowsandmilk »

peteretep wrote: post #46
systemvoltage wrote: post #42

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?

> 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?

OS X apps share frameworks in the user space, while docker images don’t...and docker images have all the constraints everyone hates about sandbox, but only make it worse. E.g. the file open dialog in macOS will grant apps access to the file when the user chooses the file. In docker, I have to manually add a path whenever I want tools to have access.

Re: Run More Stuff in Docker

#56

Post by harryruhr »

Docker has its use cases. But running everything possible in a docker container just for the sake of "dockerizing" seems a little bit excessive.

One must basically maintain a (more or less) complete userland environment for every application. The idea of shared libraries is taken to absurdity this way. It would be better to build all static.

Then there is the waste of resources. I'm sure with plenty GB RAM, TB of SSD space and GBit of bandwith available nowadays many people don't notice. But for what?

Re: Run More Stuff in Docker

#57

Post by cowsandmilk »

peteretep wrote: post #54
joshuanapoli wrote: post #53

Earlier quoted context omitted.

Loading a 1GB image to run a 50MB executable can be trouble. I used to work while commuting on a train on a daily basis. Unexpectedly needing a big download could ruin my morning.

Why are you running such huge images for a 50MB executable?

We expect every app developer to suddenly become an expert in efficiently producing docker layers and not just lazily use an Ubuntu desktop image?

Re: Run More Stuff in Docker

#58

Post by cinquemb »

harryruhr wrote: post #56

Docker has its use cases. But running everything possible in a docker container just for the sake of "dockerizing" seems a little bit excessive. One must basically maintain a (more or less) complete userland environment for every application. The idea of shared libraries is taken to absurdity this way. It would be better to build all static. Then there is the waste of resources. I'm sure with plenty GB RAM, TB of SSD…

> Then there is the waste of resources. I'm sure with plenty GB RAM, TB of SSD space and GBit of bandwith available nowadays many people don't notice. But for what?

Yeah, you deff notice if you are trying to scale as cheaply as possible…

Re: Run More Stuff in Docker

#59

Post by joshuanapoli »

peteretep wrote: post #54
joshuanapoli wrote: post #53

Earlier quoted context omitted.

Loading a 1GB image to run a 50MB executable can be trouble. I used to work while commuting on a train on a daily basis. Unexpectedly needing a big download could ruin my morning.

Why are you running such huge images for a 50MB executable?

Probably because container authors learned from Docker's getting started video, which demonstrates a 1GB "hello world" image.

Re: Run More Stuff in Docker

#60

Post by peteretep »

cowsandmilk wrote: post #57
peteretep wrote: post #54

Earlier quoted context omitted.

Why are you running such huge images for a 50MB executable?

We expect every app developer to suddenly become an expert in efficiently producing docker layers and not just lazily use an Ubuntu desktop image?

I expect anyone distributing their app via Docker to learn how to use their tooling properly, yes?
Post reply on HN