Live data from Hacker News

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

docker.com

141–150 of 334 posts

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

#141

Earlier quoted context omitted.

If you want actual reproducable, actual portable software, Nix. Otherwise there are countless other OCI runtimes, cri-o, containers, etc. Kubernetes doesn't even use Docker. What a thing, docker. I can't get over the staying power it has had despite... Everything.

How do I run the ecosystem the docker already has with nix alone? It's not just the runtime.

[deleted]

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

#142
post #119

Earlier quoted context omitted.

(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…

>Actually... they aren't contradictory. They are. Your intent may not have been contradictory, but the messages received by everyone else were contradictory. You should own that if you are serious about doing better. Your intent doesn't really matter in these situations.

Yeah, really weird that after an apology announcement they’re still defending the original message at all. Not too hard to say “Yes, those messages contradict each other. The first one did not communicate our actual plan. The second message is a correction and clarification.”

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

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

On the other side of the spectrum, working somewhere that would have purchased thousands of licenses, they were equally unaware of what larger corporations want or need for such arrangements.

They were so blinded by giant dollar/Euro signs when insisting that we take loads of those ~20/month licenses that included a lot of things that are anti-features to most enterprises (we need to prevent people from pulling/pushing to Docker Hub!) but left out things that would make it less miserable (SSO/SAML), that they couldn't see that absolutely no one was going to put five figures on their corporate card each month.

I see that they now have those things, but it would have been very clever to have asked a few potential customers about these things ahead of time, and made sure they had them as soon as they stuck their hands out... or had a few ex-corporate types around to run this all by before telling us that we will be buying Docker licenses within 120 days for everyone who happens to have Docker Desktop installed. At least they were savvy enough to realize that large companies couldn't have begun to cope with much less notice, but as it was, the rough start with a looming deadline was enough motivation to get us trying alternatives right away.

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

#144
Monetizing what we took for granted as available for free has really rubbed everyone the wrong way. I've noticed teams are much less likely to request paid Docker Desktop, especially since there are perfectly suitable free alternatives nowadays. We all use either native docker engine on Windows + WSL2, or the MIT licensed Colima on Mac. Honestly, Docker Desktop was always a fairly heavyweight and cumbersome app with a very high opinion of itself.

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

#145

Earlier quoted context omitted.

Ah, the good ole "my company won't pay for a $5/month tool that I like because the tool maker won't invoice my company for less than 50 users, so instead of paying $5/month myself on my credit card, I literally 'can't use it anymore' out of principle."

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 could be construed as corruption — unless you’re reimbursed, but it’s above the threshold…

This whole thread has given me flashbacks to that time when the project manager broke down in tears and put his credit card back in his wallet…

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

#146
post #66
post #6

Earlier quoted context omitted.

One of the difficulties of public relations is communicating to multiple audiences at once. One of Docker’s audiences are the paying customers who outside that 2% and would want some assurance that if docker makes errors, those errors are smaller in magnitude. This statement seems like it is aimed at assuaging the worries of that audience. Is it good practice? I do not know.

> One of the difficulties of public relations is communicating to multiple audiences at once. Why not just release multiple statements and links? "Click here for customized PR statement if you are a open source developer" "Click here for customized PR statement if you are a closed source developer" "Click here for customized PR statement if you are an executive who can't code" "Click here for customized PR statement…

ChatGPT> Could you rephrase the PR statement to the ad profile of this HTTP client?

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

#147
post #24

Earlier quoted context omitted.

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 distrib…

They also are saying the maintainers will be unable to update the images after the 30 days. So the panic and bitching are perfectly deserved: https://news.ycombinator.com/item?id=35188691

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

#148
post #125

Earlier quoted context omitted.

>>>During that period you will maintain access to any of your public images. What did this mean in that case? That the images will continue to exist but the maintainers cannot update them? They'll just become orphaned?

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

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

#149
post #125

Earlier quoted context omitted.

>>>During that period you will maintain access to any of your public images. What did this mean in that case? That the images will continue to exist but the maintainers cannot update them? They'll just become orphaned?

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

So, any public image where the maintainer doesn't jump through hoops gets frozen in time, unable to be updated, and starts accumulating CVEs? This sounds worse than deleting the image.

Any smart FOSS maintainer will find alternate hosting...

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

#150
post #119

Earlier quoted context omitted.

(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…

>Actually... they aren't contradictory. They are. Your intent may not have been contradictory, but the messages received by everyone else were contradictory. You should own that if you are serious about doing better. Your intent doesn't really matter in these situations.

It is important to understand that most corporations do not apologize, ever, unless there is a direct threat to cash flow.

This behavior is now demonstrated, it is the desired relationship, and it will be the baseline, all protestations aside.

The apology is meaningless. If this is not what you want, then take steps to limit the damage done to you, and do it now.

Post reply on HN