Live data from Hacker News

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

docker.com

71–80 of 334 posts

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

#72
They say that their separate "open source program" (DSOS) is completely better than Free Teams. Why didn't they just migrate everyone on Free Teams to DSOS and then worry about the qualifications for those migrated afterwards (and less stringently)?

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

#73
post #55
post #27

Earlier quoted context omitted.

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.

I have many issues with Docker the business but, have to say, this situation sounds like they might not be the problem quite as much as the employer.

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

#74
post #61

It's almost becoming a cliche for companies to release damage control follow-ups like this after they pull a bait and switch. It's always "we're sorry that we didn't communicate our bait and switch effectively". Not we're sorry that we pulled a bait and switch. We're sorry you didn't understand the value in this bait and switch. It's your fault, actually. But we're sorry you're angry. Now stop giving us negative atte…

The forces of capitalism reward this, it will continue to happen as long as we pick pure capitalism as a system, and keep assigning values to companies purely on financials with no consideration toward their ability to empathize and communicate.

There's no such thing as "pure capitalism" – not if you're talking about things that exist.

In an ideal free market with perfectly-rational omniscient actors, this issue wouldn't occur. I don't think you even need the omniscience: trust, memory, reputation/vouching and basic game theory should be sufficient (though I haven't proven this). Alternatively: a free market with contracts, where all things go through the system, would work.

In the real world, the system consists of people, each of whom is optimising for a particular thing. Very few people are optimising for "make the most money, at the expense of all else". Show me anyone (even a billionaire), and I'll show you somebody who values other things higher than the accumulation of money. And plenty of things don't go through "the system of capitalism": we have commons, and volunteers, and favours, and coerced unpaid labour / wage theft.

"The forces of capitalism" might be a good shorthand for the reasons behind this problem, but it's not strictly an accurate one: these issues aren't inherent to capitalism. They're not problems with capitalism, but problems with this system. (Capitalism does have other, different problems that are pretty baked in, like how capital is power and power lets you accrue capital, but I don't see how that relates to this issue.)

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

#75
This isn't a good clarification. While Docker says they will not delete images, it doesn't clarify whether they will delete organizations. Indeed, under "Can someone else squat my namespace?", it says "if your organization is suspended, deleted, or you choose to leave Docker voluntarily", which implies that orgs may also be deleted involuntarily. This is still a problem.

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

#76

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…

[flagged]

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

#77
post #59

Earlier quoted context omitted.

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.

I think that's what they're trying to say: you're not an affected user if it's not your image, because you can't download it in the first place.

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

#78

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…

Exactly ! I remember the original email mentioned deletion and now they say "we never said that". Time to get rid of Docker in our world.

With what?

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

#80

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…

That depends on what "organization data" means. Does that phrasing cover the images or just the existence of the organization in Docker (i.e. deleted organization)?
Post reply on HN