Comment by josegonzalez | Hacker News Reader

Comment by josegonzalez | Hacker News Reader

Whats phenomenal about this so far is that the email does not indicate:

    - what actually will happen to teams that don't become paid
    - what will get deleted on which timeline
    - whether others will be able to typosquat the images after the teams get deleted
    - how folks might handle cases where a team is owned by an oss org and has no central billing thing (fairly common)
    - how we might better handle bot users as part of paid teams

Also great is that the only way I'd know this was going on is by checking my email - I quickly went to their blog to look and didn't find anything relating to this email.

If anything, I'd want to convert my teams (dokku and gliderlabs) _back_ to single accounts, but there doesn't seem to be a way to do that.

I get that there is a need to make the company profitable but maybe spend more than 5 minutes crafting the email and thinking of outcomes for your users (who are already pissed at your pricing changes). This only makes me feel like I should move my hosting to something paid (ECR?), delete the org, and then typosquat the images.

Maybe I'm cynical, but in leaving so many critical information points out, Docker appears to be fear mongering organizations into paying for a subscription. If they provided answers to all these points, then orgs would be able to make a logical decision. By leaving these questions unanswered, orgs are incentivized to move to paid just to avoid any unknown consequences.

I have an idle team to hold a namespace for brand protection / to prevent squatting on the namespace that matches my GitHub organization.

Since the Docker daemon defaults to using Docker Hub, this feels like a dirty move to me. If I want 2 members to ensure someone can always control that namespace, do I have to pay $240 per year now?

I’d pay $20 per year for that since it helps prevent large scale squatting, but $240 per year under the threat of deletion feels like extortion.

GitHub Container Registry is a decent option for orgs, open source and private. I believe it's free to host public images and private images are just tied into your GitHub billing.

Except that the docker cli defaults to the https://hub.docker.com registry.

Meaning if you do

    docker pull rust

it'll get it from https://hub.docker.com/_/rust

Then there are namespaced things, for example your new product, mattrick/awome-flobbergator

How to install? Docker.

    docker pull mattrick/awome-flobbergator

    Using default tag: latest
    Error response from daemon: pull access denied for mattrick/awome-flobbergator, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Every time someone needs to prefix it with ghcr.io to make it pull from GitHub.

We shouldn't do

1) default registries

2) when we post documentation online we should be explicit as to what the registry is

This is all part of docker's master plan.

You can see it with more clarity here:

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

or here:

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

so redhat's podman clone of docker allows this:

https://halukkarakaya.medium.com/how-to-configure-default-se...

Reply on news.ycombinator.com