that’s really cool. i wonder if many apps would benefit from being container based? you would have a rock solid Debian base install with containers on top.
After reading this issue on github about Paperleass and gs problems I think it would be good to have this running dockerized, it will break again in the future.
Also it is bad that the update was released for the Yunohost app when not all requirements are fulfilled.
Thanks for the effort.
Sorry for leaving this here, I have no clue, so I asked ChatGPT about that problem, here is the reply:
To prevent your Continuous Integration (CI) process from running into Docker Hub’s rate limits, you can consider several strategies:
Authenticate with Docker Hub: Even if you’re pulling public images, authenticating with Docker Hub increases your rate limit. Make sure your CI system is using an authenticated Docker Hub account.
Use a Docker Registry Mirror: Set up a local mirror of Docker Hub or use a cloud provider’s registry mirror. This can reduce the number of requests to Docker Hub, as images are cached locally.
Optimize Docker Image Usage:
Reduce the number of image pulls by optimizing your CI pipelines. Cache images where possible.
Use smaller, more efficient base images to decrease the frequency and size of downloads.
Avoid unnecessary docker pull commands in your CI scripts.
Docker Hub Subscription: Consider subscribing to a paid plan on Docker Hub if your usage is consistently high. Paid plans offer higher rate limits.
Self-Hosted Docker Registry: Host your own Docker registry for your images. This approach gives you full control over your registry without external rate limits.
Rate Limit Handling in CI: Implement logic in your CI pipelines to handle rate limiting, like retries with exponential backoff.
Use Alternative Registries: Leverage other container registries like GitHub Container Registry, GitLab Container Registry, or Amazon Elastic Container Registry, which might offer better or different rate limits.
Monitor and Analyze Usage: Regularly monitor your Docker Hub usage to understand and optimize your pull patterns. Tools and logs can provide insights into how often and what your CI is pulling.
Each of these methods has its own trade-offs in terms of complexity, cost, and maintenance. You may need to use a combination of these strategies based on your specific CI workflows and requirements.
