News for hackers. Stuff that matters.
Re:AWS pre-announces public container image registry by sneak on Monday November 02, 2020 @11:29PM (#24976296)
> This is how you get people to stop doing nice things like writing open software.

Docker stopped making open software before they limited the pulls. Docker Enterprise for Windows (Windows dockerd, basically), Docker Desktop for Mac, and Docker Desktop for Windows are all closed-source and proprietary.

Docker-the-company hasn’t cared much for open source in a while.

Re:AWS pre-announces public container image registry by m463 on Tuesday November 03, 2020 @01:32AM (#24976964)
the thing that annoyed me was the telemetry in the mac installer before you even did an install.

Additionally they made it hard to do a personal registries, which is what's going to happen now anyway. I think they tried to keep themselves in the loop too much, because it's valuable for business and monetizing was a long term goal.

here's the thread I saw:

https://stackoverflow.com/questions/33054369/how-to-change-t...

pointing to this:

https://github.com/moby/moby/issues/7203

and also there was this comment:

"It turns out this is actually possible, but not using the genuine Docker CE or EE version.

You can either use Red Hat's fork of docker with the '--add-registry' flag or you can build docker from source yourself with registry/config.go modified to use your own hard-coded default registry namespace/index."

Re:AWS pre-announces public container image registry by sneak on Tuesday November 03, 2020 @05:52AM (#24978398)
Docker Desktop is terrible spyware. I managed to crash it a few times recently and intercepted the reports before they were sent off; it collects a ton of sensitive information about your computer in the crash report it sends, including pcap logs(!).

I’ll never run code from them I didn’t build myself. That company is super shady now.

Re:AWS pre-announces public container image registry by djrobstep on Tuesday November 03, 2020 @05:59AM (#24978437)
What's the hard aspect of doing personal registries? I found it easy enough, although only set up something very basic.
Re:AWS pre-announces public container image registry by curryst on Tuesday November 03, 2020 @02:07PM (#24982829)
It's not hard, it's just clunky. You have to put the full URL of your Docker registry every time you reference the image. There's no way to say "just always use this registry instead".

I haven't found it terribly difficult to set up either, just annoying.

Re:AWS pre-announces public container image registry by zapita on Tuesday November 03, 2020 @07:23AM (#24978971)
Didn’t they just stop launching new OSS projects, and focused on maintaining what they already have launched? They’ve been criticized a lot over the years (correctly, I think) for lacking focus. Are we now criticizing them for narrowing down their focus?
Re:AWS pre-announces public container image registry by bdcravens on Tuesday November 03, 2020 @06:38AM (#24978691)
I'm not sure they ever followed through completely, but that was part of the idea between Docker/moby
Re:AWS pre-announces public container image registry by nickstinemates on Tuesday November 03, 2020 @12:49AM (#24976766)
Sad times