I’d like to host my own container images centrally in my network so that I can both cache the images (if dockerhub or similar goes down) but also host my own images that I don’t want public. Anyone doing this?

  • zelifcam
    link
    English
    1019 hours ago

    Gittea and Forgejo both have self hosted container registries.

    • lemmyng
      link
      fedilink
      English
      623 hours ago

      Does registry still have that problem of making it practically impossible to do garbage collection on old images?

  • DasFaultier
    link
    fedilink
    English
    171 day ago

    Try goharbor.io, that’s what I use. I think (but I’m not sure) that Forgejo/Gitea and Gitlab can also cache images.

    • @[email protected]
      link
      fedilink
      English
      41 day ago

      Can confirm, gitlab has a container registry built in, at least in the omnibus package installation.

  • @ogarcia
    link
    English
    422 hours ago

    Apart from the registries you have in GitLab and GitHub if you are looking for something more generic like Docker Hub you have Quay (from RedHat). It works very well and has a pretty nice interface (especially the new one that is in testing).

    • @fluckx
      link
      English
      2
      edit-2
      18 hours ago

      I looked into that at one point, but 15$/month is quite steep just for that ( imo )

    • @philthi
      link
      English
      222 hours ago

      I moved to quay.io years ago and have never looked back.

  • @kolorafa
    link
    English
    223 hours ago

    You can use (self hosted) gitlab as a registry storage. We do that locally so we have both code, pipeline and containers in the same place.

  • @beerclue
    link
    English
    21 day ago

    We’re using a self hosted Nexus instance at work. You probably don’t need all the features it offers, but it does its job really well. For free, too.