Live data from Hacker News

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

docker.com

211–220 of 334 posts

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

#212

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…

(from Docker DevRel team) > Given these statements directly contradict each other Actually... they aren't contradictory. The organization data will be retained for 30 days and is subject to deletion. That data includes the teams, memberships, etc. But, it wasn't clear what we were going to do about the images. Keeping the public images is important as many other images build on top of them. > It feels like they chang…

Face it, you're on heavy damage control and it just seems... untrustworthy.

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

#213

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…

This is why I believe that they changed what would happen after the pushback and are trying to hide that they changed.

In reality they were probably just going to disable access to updating all along and then maybe someday delete things, but didn’t want to say exactly that.

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

#215

Faq does not include the most asked question: "Why the fuck are you still so bad at this?"

(from the Docker DevRel team) Ha! Just had to say... this gave me a good laugh! We're trying to get better... I swear! Comms are hard. We'll get there.

Appreciate it. I'd advise to try hard to not be dismissive of even the more snide and flamey comments in this thread - their interpretations are valid from what I see posted so far.

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

#216
post #87
post #78

Earlier quoted context omitted.

With what?

Podman is pretty good, and more or less a drop-in replacement.

Yep, already wrote an internal guide for my whole team to move away from docker into podman+quay.io by the end of next week.

Works like a charm on our macbooks, very neat.

Even if we need to pay, I’m looking for alternatives not Docker Inc. - There is only so much you can take.

I don’t want to rely on them anymore.

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

#217
post #65

Earlier quoted context omitted.

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

Pretty hard to get NET30 invoicing on a transaction which is less than $450, especially if you've chosen the monthly plan. It's just not worth the labor chasing an unpaid $450 invoice every damn month.

Isn't that what resellers are for?

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

#219

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…

(Docker DevRel team here) For clarification, the program grants one year of access, but is indefinitely renewable as long as the program is still compliant with current criteria.

Is this renewal automatic? Having to go recertify with docker once a year for my tiny open source project that we happen to have an image for is literally infinity percent more hassle than I would like to deal with.

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

#220

Earlier quoted context omitted.

They really think we're idiots!

Relying on a free service for important work? Maybe they are right.

Silly us, I suppose we should stop relying on APT/RPM/what-have-you Linux package mirrors, NPM, NuGet, PyPi, Hex, RubyGems, Crates, ... too.
Post reply on HN