Live data from Hacker News

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

docker.com

41–50 of 334 posts

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

#42

The third sentence in their apology is "This impacted less than 2% of our users." What is that supposed to convey? It feels like a handwave. 'We're sorry we mistreated you, look how small you are to us.'

Ever wonder why Google outage notifications always say stuff like "this impacted 0.01752% of users"? Because if they leave that out, the PR department ends up flooded with questions from reporters about "how bad was this outage, exactly?", and less-diligent publications running "Google suffers massive outage" headlines.

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

#43
post #24

Earlier quoted context omitted.

The 2% they’re referring to are businesses that are using Docker’s hosted services for free. The majority of the outrage was from people thinking about the non-business users, that is, open source projects, which Docker unintentionally implied would be impacted by this change. Docker are apologising for their poor communication which made people think this change applied to more than just a tiny portion of the user b…

Anybody who uses "docker pull" or "FROM" and not pointing at their own hosting or their own paid Docker account was affected as evidenced by the thousands of comments worried about the impact.

[deleted]

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

#44

Not sure how this changes anything. Their open source program [1] only grants a free 1-year Docker Team subscription. After which time the whole system is unusable. And most of those features aren't what open source teams even need which is surely just basic multi-user access. They really should have just tightened the entry criteria for their open source offering if they were so concerned about it being misused. htt…

I think I read that it prohibits making money, like consulting on the OSS product. This prohibits a lot of OSS teams.

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

#45
Two solutions that don't seem to be mentioned:

1. Let any user have how many "free teams" they want, but restrict the image size (under 1GB?) and/or downloads (under 1,000/month?). Maybe let the community vote for open source images exempt from this restriction.

2. Run a free link redirect service: user registers my-team on hub.docker.com, links my-team/my-image with their preferred registry my-registry.com, client-side docker pull my-team/my-image resolves automagically to my-registry.com/my-team/my-image.

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

#47
post #27
post #13

Ah, good ole Docker. When they did the "it's not free anymore" rugpull on Docker Desktop, I couldn't use it at work anymore since they wouldn't invoice us for less than a 50 seat license. Unfortunately, a lot of businesses won't buy things without invoicing for legal reasons. It really upset me because I had a pretty solid workflow with docker desktop on a mac. Now I can't use that anymore. I am not surprised they co…

I get invoices for my $5 Pro plan. Do you mean they wouldn't take the order on credit?

Probably means they would not do NET30 or the like terms to fit with their corporate purchasing workflow.

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

#49

The third sentence in their apology is "This impacted less than 2% of our users." What is that supposed to convey? It feels like a handwave. 'We're sorry we mistreated you, look how small you are to us.'

The most favorable percentage possible, probably. Rather than percentage of requests, percentage of active users, etc.

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

#50
post #37

So if it's only such a small amount of accounts, then surely it's barely a line item. Makes no sense, something doesn't add up here.

I would guess that those 2% of users account for more than 2% of the load on Docker Hub. Open source projects on a regular release cadence would push images more frequently than your average user, and those public images from the projects themselves were probably used in FROM statements more frequently than other images.
Post reply on HN