So can team members still push security updates to an image on a public team account that’s not in their FOSS program? It’s still incredibly unclear if this is allowed, or if the existing images will be frozen in time until someone pays for the account. Still a nightmare for CISOs that rely on the ecosystem.
We apologize. We did a terrible job announcing the end of Docker Free Teams
221–230 of 334 posts
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#222Earlier quoted context omitted.
(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.
Thank you for the clarification. For reference, are there any open source projects you've seen that suddenly change course to being paid products and would lose open source status according to Docker? Any Linux distros that suddenly went closed source? Are there any sort of general public licenses that might preclude projects from even doing so?
Say a distro sells laptops with the distro pre-installed while also providing the same image online and might also sell consulting services to companies utilizing the distro.
According to my undestanding of the terms of Docker's opend source program, even if said distro was fully open-source and a run by a non-profit they would be non-eligible to participate in the program.
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#223Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#224Earlier quoted context omitted.
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...
> Any smart FOSS maintainer will find alternate hosting... I think that’s obviously the point of the whole exercise — pony up or leave. They’re just doing it in an annoying manner
Can't believe how soon this announcement came after the redhat "we're killing centos support now, best of luck". It's pretty clear how this industry reacts to major support changes with no heads up.
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#225> This impacted less than 2% of our users. Ah, only 2%. Completely irrelevant number. Move along.
It baffles me that, for such small quantities, they don't just "grandfather" existing users and only change conditions for new signups.
The insignificant problem would sort itself out in time, instead of creating a lot of friction and a plume of dumpster fire smoke, for very little or no gain at all.
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#226Previous 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…
So you’re going to continue to host images that have severe remote code execution exploits?
With no way for the person who posted them to ask people not to use them?
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#227Earlier quoted context omitted.
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.
Any chance of seeing a version of that guide outside of your organization?
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#228Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#229Previous 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…
sooooooooooooooooo orgs that didn't want to upgrade are still left with users pinned to old address of the image with no option to push security updates?
Re: We apologize. We did a terrible job announcing the end of Docker Free Teams
#230I'm a bit surprised that they are struggle to make $$ with such a popular tool. But I could be wrong.