Thanks for all the great replies!

  • @just_another_person@lemmy.world
    link
    fedilink
    English
    284 months ago

    Retag and push to a local registry. Lots of options out there for setting one up.

    Honestly, you already have the image locally if you’ve pulled it. You don’t really need to run a registry unless you’re dead set on it. You can also flatten and export containers for backup if you really want.

    • @thirdBreakfast@lemmy.world
      link
      fedilink
      English
      164 months ago

      Two good points here OP. Type docker image ls to see all the images you currently have locally - you’ll possibly be surprised how many. All the ones tagged `` are old versions.

      If you’re already using github, it includes an package repository you could push retagged images to, or for more self-hosty, a local instance of Forgejo would be a good option.

      • Foster Hangdaan
        link
        fedilink
        English
        94 months ago

        I’d also like to add that you can save an image to a local file using docker image save and load them back using docker image load. So, along with the options mentioned above, you have plenty of options to backup images for offline use.

    • Rikudou_Sage
      link
      fedilink
      English
      64 months ago

      Honestly, you already have the image locally if you’ve pulled it.

      I guess not everyone treats their PC as an ephemeral storage, huh? I don’t trust anything that’s available only locally to survive.

      • @just_another_person@lemmy.world
        link
        fedilink
        English
        64 months ago

        Well the question is about a container disappearing from a public registry, in which case nothing would happen if it’s already pulled locally. Figuring where to go from there is the other half of that problem.

    • @precarious_primes@lemmy.ml
      link
      fedilink
      English
      34 months ago

      We run this at work so we have forever copies of image tags and to reduce dockerhub rate limit issues. Works well even for a large dev team.

  • Scrubbles
    link
    fedilink
    English
    3
    edit-2
    4 months ago

    For most of you suggesting hosting a repository - yes but,

    Host forgejo. Just host the git mirror. It comes with a package repo out of the box. Then you have the source code and the docker images

  • hyperreal
    link
    fedilink
    English
    24 months ago

    I don’t know if this will help you, but I wrote a tutorial on how to setup a local registry on the LAN on a Fedora Server or RHEL-compatible server. https://techne.hyperreal.coffee/tutorials/setup-a-lan-container-registry-with-podman-and-self-signed-certs/

    But anyway, it’s unlikely docker.io or quay.io or ghcr.io will go completely offline. If anything they might experience a DDoS, in which case I imagine they have competent devops employees who would ensure they become functional again within a matter of hours.

  • Cousin Mose
    link
    fedilink
    English
    04 months ago

    Isn’t a Docker registry just HTTP? Would a caching proxy be too hard to use for this?