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

We apologize. We did a terrible job announcing the end of Docker Free Teams

docker.com

Post reply on HN
Print view View original

281–290 of 334 posts

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#281

Post by [deleted] »

jiggawatts wrote: post #145
floatinglotus wrote: post #128

Earlier quoted context omitted.

That’s not the problem. The problem is that companies forbid their employees from using it if they can’t pay for it.

I love big enterprise, where ten people can have daily meetings for a month to decide how to pay a few hundred dollars. Yes, this happened to me. More than once. No, you can’t just pull your wallet out and offer to pay for it yourself with cash. You’re not an “approved supplier” and it’s the supplier that needs to provide warranty support. Also if you pay for it yourself, then you’re providing it as a “gift” and that…

[deleted]

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#282

Post by diffeomorphism »

bragr wrote: post #148
mikesir87 wrote: post #131

Earlier quoted context omitted.

(from the Docker DevRel team) "During that period" refers to the 30-day period. During that time, the images are accessible. After the 30-day period, they will still be pull-able, but not able to be updated.

>accessible >pull-able To any reasonable average person, these mean the same thing.

Absolutely not. For users, yes. For the person uploading/modifying the image, hell no.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#283

Post by francislavoie »

TheDong wrote: post #271
pmoriarty wrote: post #240

Earlier quoted context omitted.

"somewhat irresponsible for the `latest` tag. A `latest` tag that cannot be updated is ... worse than no `latest` tag" What's irresponsible is relying on a "latest" tag for updates.

The irresponsible thing is making it so the tag exists, but the organization behind it cannot update it. Let's take for example the "jenkins/jenkins:latest" image. Jenkins is notorious for having security updates, so in 2 years, if the latest tag is still there and frozen, it will be an attractive nuisance, causing people to download insecure software... That's what the parent comment is trying to say. It's irrespons…

You missed his point. He's saying "latest is an anti-pattern". Which is correct. Everyone should be pinning to specific versions or semver to avoid being accidentally upgraded to a release with breaking changes.

Yes, obviously making existing tags immutable is bad. Nobody is disputing that.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#284

Post by francislavoie »

worksonmine wrote: post #165
djha-skin wrote: post #108

Earlier quoted context omitted.

rolls eyes OR, their marketing and DevRel departments and their engineering departments simply had a miscommunication; when it was realized, the present post was composed. This kind of thing happens inside companies all the time, including the one you're probably working at right now. No need to get up in arms over it.

I don't believe it was a miscommunication. Even if it was a company as important as Docker inc, mentioning DELETING containers requires some care and should raise some flags at any serious communications department. This is not just the wrong date for a convention in the newsletter. What impact does it have on the ecosystem they've built? Some really serious projects use Docker and even if they have their own reposit…

Nomenclature nitpick: "deleting images", not "deleting containers". Images are what they host. Containers are running instances of an image.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#285

Post by code_biologist »

francislavoie wrote: post #283
TheDong wrote: post #271

Earlier quoted context omitted.

The irresponsible thing is making it so the tag exists, but the organization behind it cannot update it. Let's take for example the "jenkins/jenkins:latest" image. Jenkins is notorious for having security updates, so in 2 years, if the latest tag is still there and frozen, it will be an attractive nuisance, causing people to download insecure software... That's what the parent comment is trying to say. It's irrespons…

You missed his point. He's saying "latest is an anti-pattern". Which is correct. Everyone should be pinning to specific versions or semver to avoid being accidentally upgraded to a release with breaking changes. Yes, obviously making existing tags immutable is bad. Nobody is disputing that.

There are exceptions though. I'm the kind of person that would pin Jenkins to latest even if it is an antipattern. I'm way more concerned about security flaws than a temporary CI breakage. So for me: Everyone should be pinning Jenkins to latest to avoid accidentally staying on a release with security holes.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#286

Post by technick »

manifoldgeo wrote: post #198

> This impacted less than 2% of our users. I think they mean it impacts less than 2% of user _accounts_. Not every account is created equal. If you were an open-source org with millions of image downloads a month, having your org deleted would have an outsized effect on the community. Many more Docker Hub users than 2% stand to be affected by these changes, even if the nominal value of 2% of user accounts is accurate…

Oh my, have you ran a `docker search gaslight`? I just did and it looks like docker hub is being used to distribute ebooks? WTF... This is why we can't have nice things....

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#287

Post by technick »

I expect a third round of apology emails from Docker with less gaslighting and real numbers of how this affected 20k users.. or maybe more, not in a 2% format.

Depending on how this goes I might let my purchasing department know it's time to cancel our enterprise subscription with Docker. I have a IBM RH corp account and would much rather pay RH at that point because Docker is burning all of it's cred in the dumpster out back.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#288

Post by dasfsi »

technick wrote: post #286
manifoldgeo wrote: post #198

> This impacted less than 2% of our users. I think they mean it impacts less than 2% of user _accounts_. Not every account is created equal. If you were an open-source org with millions of image downloads a month, having your org deleted would have an outsized effect on the community. Many more Docker Hub users than 2% stand to be affected by these changes, even if the nominal value of 2% of user accounts is accurate…

Oh my, have you ran a `docker search gaslight`? I just did and it looks like docker hub is being used to distribute ebooks? WTF... This is why we can't have nice things....

Not quite distribute, it feels like spammers are using dockerhub pages as a free publishing platform for posting links to even more scummy websites in promises to get free ebooks and full hindi movie downloads and my favorite "cleanmymac-x-443-cracked-activation-code-hot".

Docker probably should've started their purge there, not with FOSS orgs...

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#289

Post by bleuchase »

dheera wrote: post #267
bleuchase wrote: post #199

Earlier quoted context omitted.

Is that a serious suggestion? Who on earth would take the time to look through all of those to see which one best fits them? Companies have enough trouble getting press releases read already.

I guess then you could use some heuristics and ChatGPT to tailor the press release to the particular viewer. For example if the user has a screen resolution of three 4K monitors side by side, using Linux, and coming from a Silicon Valley IP address, they are probably a developer. If they have the screen resolution of an iPad Pro and a New York IP address they are probably an executive on the go. The HTML5 acceleromet…

That could be a more effective approach.
Post reply on HN