Live data from Hacker News

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

docker.com

51–60 of 334 posts

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

#51

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.'

This is how i interpreted this. I feel this was a box ticking exercise with 0 emotion.

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

#52
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…

Hey! They decided to do invoicing, after all! When they couldn't find a way to take purchase orders in the initial license obligation round and we were going to have to go through a third party licensing service to pay, we did a little math, and realized that it was cheaper to let one of the guys on the DevOps team create and maintain the customized WSL install option, with the bonus of steering the developers to our internal registry out of the box, because we really don't want devs pulling stuff directly from Docker Hub without any sort of traceability, much less (shudder) pushing anything there. The prospect of having to manage hundreds (or more) of user accounts with SSO "on the roadmap, pinky swear" pushed the math over the top.

Many months later, this is still proving to have been a good call.

Moral of the story: do not try to shove a category change on large corporations without having basic things large corporations routinely require in order to give you money, especially if replacing you requires a lot less spend on extra internal labor and material than you're demanding to be paid.

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

#53
post #25

I’m guessing they did this change because the cost of giving a free service isn’t cheap for docker?

It seems the concept of a loss leader is "lost" on Docker. Some MBA with a spreadsheet at Docker hasn't realized that where the upstream OSS goes, the rest follow.

Loss leader for products that don't sell? The change to a full open source toolchain for their core products was more or less painless.

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

#54
post #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.

Obviously but they should use that metric of resources used vs how small the impact is.

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

#55
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?

I assume they mean Docker issues an invoice which the company's AP department can then pay by either cutting a check or ACH transfer. At least that's what we had to get all our vendors to start doing when the company I worked for killed off corporate cards and quit letting employees expense things like this.

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

#56
Previous communication:

> If you don't upgrade to a paid subscription, Docker will retain your organization data for 30 days, after which it will be subject to deletion. During that period you will maintain access to any of your public images.

New communication:

> We’d also like to clarify that public images will only be removed from Docker Hub if their maintainer decides to delete them. We’re sorry that our initial communications failed to make this clear.

Given these statements directly contradict each other I am a bit surprised this is called clarification. It feels like they changed the actual strategy, not just the communication around it.

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

#58
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.

Well, they say they were never actually affected

> We’d also like to clarify that public images will only be removed from Docker Hub if their maintainer decides to delete them.

> Will open source images I rely on get deleted?

> Not by Docker. Public images will only disappear if the maintainer of the image decides to proactively delete it from Docker Hub. If the maintainer takes no action, we will continue to distribute their public images.

People may have thought they were affected, which is what they seem to be apoligising for.

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

#59

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.

It's really misleading though, as it only reflect the owners of the images. Presumably I should count as an affected user if I don't own the image, but try to download it.

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

#60
> How can I see if I’m affected?

> Please consult the Organizations page of your Docker account; any affected organizations are labeled “Docker Free Team” in the “Subscription” column. Less than 2% of Docker users have a Free Team organization on their account.

Interesting theory, but no; my account is paid, but I'm using third party images that are rather harder to verify.

Post reply on HN