Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's true that you don't, but I can see the advantages.

I have a Raspberry Pi that is natively running a scraper using headless Chromium and cron. It works great, except....

I ended up needing a virtual framebuffer. I got it working on the Raspberry Pi, but I got a new workstation and wanted to edit my script and test it there. I got cryptic errors that I needed to debug to understand they were framebuffer issues, then attempt to recreate the setup that's running on my Pi, then debug that.....

My first mistake was not writing down what I did in my README, but a Docker image would have saved me a ton of time here.



Why couldn't you keep editing your script in your Pi?

Isn't proposing Docker as a solution to this going nuclear?

I think there are some many cheaper things you can do to solve this.

For me this is absolutely no justification for Docker use in this scenario.


The script takes 60+ seconds to run on an RPi and fewer than 10 on an i9, allowing for significantly faster iteration.


Doesn't really answer any of the questions of what docker actually does to help here, other than make everything slower and more complex.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: