-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
marp-cli docker pull rate limited #577
Comments
The rate limit is associated to the account of user who tried to pull. The pricing plan of our Docker ID (marpteam) should not matter. To avoid pull rate limit error, I recommend to add the login step by Even so, the Docker image is providing just for the convenience to try Marp CLI, and I not recommend to use in the workflow. Installing Marp CLI in CI workflow is more reliable way to use It. https://github.com/orgs/marp-team/discussions/375#discussioncomment-4191221 |
There is no rate limit on the non-free org. Anyway that explains the issue. |
Because you asked "I'm curious if marp-cli is using free plan on Docker hub?", I have thought you are misunderstanding as that the pull rate limit for you will become no limit if https://hub.docker.com/u/marpteam became a non-free org.
This answer is targeted to GitHub Actions, but the command to run on CI is exactly same: Let us continue about publishing the image to the GitHub container registry on another issue #578. |
I'm facing some random rate limit messages when pulling marp-cli image from internal Gitlab CI (have not seen that when pulling from public Github repo). I'm curious if marp-cli is using free plan on Docker hub? I have definitely seen that causing timeouts for my own container images in the past. Docker Hub rate limiting is explained here. If that's the case, are there any plans to more images to GHRC? If not, would you accept a PR for that?
The text was updated successfully, but these errors were encountered: