AFAIK every NAS just uses unauthenticated connections to pull containers, I’m not sure how many actually allow you to log in even (raising the limit to a whopping 40 per hour).

So hopefully systems like /r/unRAID handle the throttling gracefully when clicking “update all”.

Anyone have ideas on how to set up a local docker hub proxy to keep the most common containers on-site instead of hitting docker hub every time?

  • kingthrillgore@lemmy.mlEnglish
    71·
    23 hours ago

    Well shit, I still rely on Docker Hub even for automated pulls so this is just great. I guess i’m going back to managing VMs with OpenTofu and package managers.

    What are our alternatives if we use Podman or K8s?

    • wireless_purposely832@lemmy.worldEnglish
      14·
      22 hours ago

      The issue isn’t Docker vs Podman vs k8s vs LXC vs others. They all use OCI images to create your container/pod/etc. This new limit impacts all containerization solutions, not just Docker.

      Instead, the issue is Docker Hub vs Quay vs GHCR vs others. It’s about where the OCI images are stored and pulled from. If the project maintainer hosts the OCI images on Docker Hub, then you will be impacted by this regardless of how you use the OCI images.

      Some options include:

      • For projects that do not store images on Docker Hub, continue using the images as normal
      • Become a paid Docker member to avoid this limit
      • When a project uses multiple container registries, use one that is not Docker Hub
      • For projects that have community or 3rd party maintained images on registries other than Docker Hub, use the community or 3rd party maintained images
      • For projects that are open source and/or have instructions on building OCI images, build the images locally and bypass the need for a container registry
      • For projects you control, store your images on other image registries instead of (or in addition to) Docker Hub
      • Use an image tag that is updated less frequently
      • Rotate the order of pulled images from Docker Hub so that each image has an opportunity to update
      • Pull images from Docker Hub less frequently
      • For images that are used by multiple users/machine under your supervision, create an image cache or image registry of images that will be used by your users/machines to mitigate the number of pulls from Docker Hub
      • Encourage project maintainers to store images on image registries other than Docker Hub (or at least provide additional options beyond Docker Hub)
      • Do not use OCI images and either use VM or bare metal installations
      • Use alternative software solutions that store images on registries other than Docker Hub