this post was submitted on 20 Oct 2025
487 points (98.6% liked)

Selfhosted

52403 readers
1135 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] magguzu@lemmy.ml 11 points 1 day ago (1 children)

I know this is selfhosted so most people here are hobbyists, but it's a ton of work to selfhost in enterprise setting. I'd wager 90%+ of people using image registries are using Docker Hub, GHCR, or AWS ECR.

[–] HelloRoot@lemy.lol 3 points 1 day ago* (last edited 1 day ago) (1 children)

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.

[–] arcayne@lemmy.today 5 points 1 day ago

Pretty sure you could run Pulp in pull-through mode and add your local Forgejo/whatever registry as a remote, which would at least give you a unified "pull" URL. Then just use Forgejo actions to handle the actual build/publish for your local images whenever you push to main (or tag a release, or whatever).

Pulp might actually be able to handle both on its own, I haven't ever tried though.