At that point you’re completely invested in their ecosystem and it’ll cost you triple to get out.

That’s next quarter, after I’ve got my bonus for all these savings.

IbM has entered the chat

Way above my pay grade! I would never suggest or support making such agreements, but I also don’t want to be in a position where I’d even be asked, so I’d just sit back with a bowl of popcorn

So, you changed one cloud provider to another…

But let me rephrase: cloud can be significantly cheaper - if you know what you’re doing and what you’re putting on the cloud.

I’ve been to data centres that cost as much as a decade of cloud hosting the service they were supporting (and that’s without operational costs).

Cloud is especially great for small businesses where you have two alternative options: either build your own data centre which you absolutely cannot afford (or risk making it barely operational and unreliable) or host your company at someone else’s DC - which is what cloud is, but worse (because nobody can set up so much resiliency and have so many DC techs/admins as Microsoft or Amazon).

There absolutely are situations where self-hosting is preferable, and even cheaper, but wondering “why do we place so much reliance” on cloud service providers just shows that people have no clue what cloud actually offers.

Put tariffs on everybody who doesn’t host US data on their own cloud services.

I think co-ops are the way to go, but I can understand that someone “just” wanting to purchase the good/service might not see the difference between a co-op and corporation like Amazon.

I don’t think it’s a size issue really, but co-ops generally stay smaller in part due to how they are internally organized compared to a “median” corporation.

I also think that the government actually does a pretty good job at managing things; it’s just their failures are public. Private boondoggles might drive many people into bankruptcy, but they aren’t publicized any more than absolutely necessary.

I wouldn’t want my city traffic lights managed by a private company, because they’d try to cut costs and avoid building in redundant systems.

While they aren’t run by private companies, the traffic lights at the entrances to most housing estates are procured and installed by the developer, at least in Australia. Without fail, about 12-24 months later, the red and green LED lights will have half a dozen or more dead pixels on them. Meanwhile, newer LED lights installed by the roads department are still going strong years later.

For your personal use, you don’t need an enterprise setting. It’s just a simple compose file that you run.

You can host a registry in pull through mode, so you still have all the images you use locally, but if it’s not in your registry yet, it pulls it from docker hub or whatever.

The only pain point is that a single registry can’t do both. So if you want to push your own docker images AND have a “cache” of stuff from docker hub, you need to run two registries in two different modes. And then juggle the url’s.

Harbor

I have just this (which ironically won’t work now cause docker hub is down)

services:
  registry:
    restart: always
    image: registry:2
    ports:
      - 5000:5000
    dns:
      - 9.9.9.9
      - 1.1.1.1
    volumes:
      - ../files/auth/registry.password:/auth/registry.password
      - registry-data:/var/lib/registry
    environment:
      REGISTRY_STORAGE_DELETE_ENABLED: true
      REGISTRY_HEALTH_STORAGEDRIVER_ENABLED: false
      REGISTRY_HTTP_SECRET: ${REGISTRY_HTTP_SECRET}
      REGISTRY_AUTH: htpasswd
      REGISTRY_AUTH_HTPASSWD_REALM: Registry Realm
      REGISTRY_AUTH_HTPASSWD_PATH: /auth/registry.password
      # REGISTRY_PROXY_REMOTEURL: "https://registry-1.docker.io/"

volumes:
  registry-data:

I don’t even remember how and when I set it up. I think it might be this: https://github.com/distribution/distribution/releases/tag/v2.0.0

Recently somebody has created a frontend, which I bookmarked but didn’t bother to set up: https://github.com/Joxit/docker-registry-ui