Downvote on my stackoverflow question, no answers or comments yet

BECAUSE NOBODY KNOWS THE ANSWER

Fucksticks, really hate everything software and software related, why am I doing this anymore

Ask it here. Couldn't hurt to try.

So people downvote the unknown instead of building the future... :'(

@Grumm I learned very early on that SO is readonly.

share the link here for more downvotes (or some answers... whichever button we click first)

Links or it didn't happen.

When people cry about downvotes on stackoverflow, I always wonder how they wrote the question. Some people deserve the downvote, since they can't even be bothered to format the code, for example.

@netikras that's called "the meta effect" asking about downvotes on meta.stackoverflow.com attracting even more people who get a kick out of clicking the downvote button.

Nothing against up- and downvoting per se, but why won't people even leave a short comment, raise a flag, or suggest an edit?

But if they want, they can't, because SO's edit queue is always full. StackOverflow can be a helpful resource sometimes, but often it's just an amplifier for developer frustration.

Wonder if DR would do good with a tech question category 🤔

@bigmonsterlover sad and lonely kings and queens category

@bigmonsterlover actually two categories from now on “people who fuck” and “people who don’t fuck”

@bigmonsterlover Might as well make it a political spectrum by adding “people not giving a fuck”

@bigmonsterlover https://youtu.be/UMtV90uzkEA

It's about replacing a docker container with zero downtime. Docker automatically numbers container names with _1, _2, and so on.

Okay, fine.

But if I rename this to something like _old or _whatever, or even remove the old container, if you run scale again, docker remembers the original scale number and then appends a _3, or _4 or whatever!!!!

Okay fine. Let's try another way

Searching around, the 'recommended' way is to parse your docker ps output, figure out which is the older one and then remove it??? wtf!!!!

mind boggling that (IMO what should be an essential feature of docker) can only be accomplished with some roundabout bullshit

still trying to figure out an elegant way to do this without docker's opinionated bullshittery. i'll update if i find a solution

Yep, I have a working example illustrating that a naïve re-issung of docker compose up causes downtime when docker replaces the container. Sure, its only about 2 seconds, but that's still downtime!

Oh, how far spite will get you.

Another interesting thing... docker will only "sometimes"? fully replace the container if the source code changes? If I make a small one or two character change in my source code and rebuild, it doesn't seem that docker always detects that, and a rebuild doesn't cause the container to be updated and reflect those changes. I thought it compared hashes of layers and then would replace if any change detected? To be 100% sure it WILL replace, your best of passing --force-recreate, then you'll be sure your new code is in the rebuilt container.

My opinions of docker are fading by the minute here...

@fullstackclown I have a few questions.

(I don't use docker... Sorry in advance) But do you use a load balancer between the containers ?

That way you can update containers one by one.

Yes, at least for networked services this is the proper way to do it. But now my question is for things like cron jobs, let's say they NEED to run every 500ms, how can we replace the said container without a single nanosecond of downtime (and also prevent race condition from running multiple containers)

finally time i learn how to do this properly