Live data from Hacker News

Goodbye Docker: Purging Is Such Sweet Sorrow

zwischenzugs.com

91–95 of 95 posts

Re: Goodbye Docker: Purging Is Such Sweet Sorrow

#91
post #67
post #33

Earlier quoted context omitted.

> I still really struggle to understand what the practical benefits to this kind of containerization actually are ... Here's why I started using it years ago. I had a CentOS 6 machine that I wanted to run Plex, Subsonic and Transmission on, but I couldn't, because they had different (EDIT: and conflicting) requirements for various packages. I might have been able to hack it, but it was looking really tricky. Enter Do…

If you didn't have that requirement of conflicting packages, would you still have used docker? Isn't once a year update a large security risk?

I probably wouldn't have, had there been no package conflicts.

As for security risk on the yearly update: all the services are only locally accessible. None are exposed to anyone but me. I do apply CentOS updates daily, though.

My only risk in an attacker on my LAN, and I think I have that locked down well.

Re: Goodbye Docker: Purging Is Such Sweet Sorrow

#92

Earlier quoted context omitted.

>git...LaTeX, Python, and Vim To be fair, LaTeX, git, and Vim, beyond shallow use, have fairly steep learning curves and can initially seem like a huge inconvenient mess before one learns, through trial and error, enough of the basics to really unlock enough utility to justify their use. In a perfect world we'd all first sit down with manuals/tutorials, absorb everything from the getgo, and hack away with bliss; but…

Really hard to use tools and half obsolete by some metrics. Vi predates keyboards with arrow keys and numpad. You can do most of what vim can do in any editor if you can use your keyboard effectively. Then there is the question of VI vs VIM. Some schools force students to use VI, which is really a different and antiquated beast. LaTeX lost a lot of relevance since Office 2010, that added a great equations editor and…

You totally can't do "most of what vim can do in any editor if you can use your keyboard effectively". For example: fXctX - find next X on current line, change to next X. You can, fortunately, get a pretty decent vim emulation in various IDEs.

TeX still renders equations better than Office does. Also it's programmable.

Re: Goodbye Docker: Purging Is Such Sweet Sorrow

#93

Earlier quoted context omitted.

Very true. I know a lot of people in school who have to use a generally well regarded technology, but hate it because they had to use it in a class. For example, they might see someone on github and go “oh is that github? I hate using git” when in reality they had to use it in a group project with 4 other people who have never used it, and had no understanding of branches, merging, etc. I have seen the same thing wit…

>git...LaTeX, Python, and Vim To be fair, LaTeX, git, and Vim, beyond shallow use, have fairly steep learning curves and can initially seem like a huge inconvenient mess before one learns, through trial and error, enough of the basics to really unlock enough utility to justify their use. In a perfect world we'd all first sit down with manuals/tutorials, absorb everything from the getgo, and hack away with bliss; but…

I totally agree with you. Those are _hard_ tools, and if on top of it you have the attitude of "I am just going to learn this for this class because the teacher told me too", you are definitely going to dislike it.

I think you are spot on with the intrinsic interest.

Re: Goodbye Docker: Purging Is Such Sweet Sorrow

#94
post #9
post #5

I just started using Docker again in production. And it's pure garbage when you hit a corner case, but works well when you don't. I'd like to stop using it as well.

Example?

The reason why lazy docker exists: "Something's not working? Maybe a service is down. docker-compose ps. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.

What a headache!"

And war stories like these are similar to what I have experienced: https://thehftguy.com/2016/11/01/docker-in-production-an-his...

Re: Goodbye Docker: Purging Is Such Sweet Sorrow

#95
post #9

Earlier quoted context omitted.

Example?

The reason why lazy docker exists: "Something's not working? Maybe a service is down. docker-compose ps. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the l…

Another example - Stuff like this: https://stackoverflow.com/questions/19688314/how-do-you-atta...

I just hit this one today.

Post reply on HN