merative / spm-kubernetes

This repository contains artifacts to assist IBM Cúram SPM customers in their journey to Kubernetes
Apache License 2.0
9 stars 13 forks source link

Hitting Docker Resource Limit when trying to create ChartMuseum Container #66

Closed kdombros closed 3 years ago

kdombros commented 3 years ago

I have registered with Docker Hub and authenticated, but I'm still seeing the resource limit error when I follow the steps to create the Chart Museum Docker container (as described here in the Runbook).

Is there any workaround - such as what is described for MiniKube?

LMK - thanks!

andreyzher commented 3 years ago

Hi @kdombros

Could you please post the exact commands you've executed and the resulting logs? If you had logged in previously, I suggest trying to run docker logout before attempting to login.

Thanks

kdombros commented 3 years ago

I just ran this command:

docker run --rm -d --name chartmuseum \
  -p 8080:8080 \
  -e DEBUG=true \
  -e STORAGE=local \
  -e STORAGE_LOCAL_ROOTDIR=/tmp/charts \
  chartmuseum/chartmuseum:v0.12.0

I get this output/error:

Unable to find image 'chartmuseum/chartmuseum:v0.12.0' locally
Trying to pull repository registry.access.redhat.com/chartmuseum/chartmuseum ... 
Pulling repository registry.access.redhat.com/chartmuseum/chartmuseum
Trying to pull repository registry.redhat.io/chartmuseum/chartmuseum ... 
Trying to pull repository docker.io/chartmuseum/chartmuseum ... 
Trying to pull repository docker.io/chartmuseum/chartmuseum ... 
/usr/bin/docker-current: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.
See '/usr/bin/docker-current run --help'.
andreyzher commented 3 years ago

I see you're using /usr/bin/docker-current - would this happen to be Docker version 1.13.x? If so, that is unsupported (not just by SPM for this purpose, but also by Docker Inc.) - you will need to upgrade to the latest version.

kdombros commented 3 years ago

whoops - yes it was version 1.13.1. I have now upgraded:

docker --version
Docker version 20.10.6, build 370c289

I hoped that would fix the error too, but no such luck. This is happening on a Fyre VM if that matters at all.

kdombros commented 3 years ago

Ok @andreyzher looks like this is not a surprise on Fyre: https://ibm-cloud.slack.com/archives/C09EJRGHH/p1603970144160700

I discovered I have Chartmuseum image on a local VM, so I pushed it to my CSP artifactory repository, and then pulled it from there to fire it up :-)

Push:

Pull/Run:

Close it up!

andreyzher commented 3 years ago

Glad you were able to sort it out!

In case you ever need to provision registry your own outside of our internal infrastructure, take a look at these 2 open source projects:

Closing.

kdombros commented 3 years ago

The easier solution was to just register/login to Docker Hub: https://hub.docker.com. Then from the command line issue: docker login -u username