Sample apps that use base image from Docker Hub might fail deployment due to pull rate limit #2
Description
Currently, some (at least one - the nodeJS one ) built-in examples are using Docker.io. Users might hit Docker pull rate limit. Even if there is a workaround, it requires a Dockerhub account and some specific manipulations.
Cloning "https://github.com/redhat-developer/devfile-sample.git" ...
Commit: 5ffa4845474ed8321cba9b69f47f02ca16210334 (Devfile Sample Repo)
Author: Andrew Ballantyne <[email protected]>
Date: Thu Jan 7 14:13:29 2021 -0500
time="2021-11-29T10:25:19Z" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
I1129 10:25:19.069266 1 defaults.go:102] Defaulting to storage driver "overlay" with options [mountopt=metacopy=on].
Caching blobs under "/var/cache/blobs".
Pulling image node:current-slim ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: Error initializing source docker://node:current-slim: Error reading manifest current-slim in docker.io/library/node: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit