Wave enabled pipelines hit container pull limit

Ask for help
1

Hi, I have a custom pipeline that I created with nf-core tools, that uses docker images which are pulled from a Docker hub repository. I have a pro Docker hub account and wish to use that while pulling these images.

I enabled wave in my pipeline’s config file like

wave {
    enabled = false
}
tower {
   accessToken = “——————————————————————————————————”
}

I have also saved my docker hub read-only access PAT that works for docker login in my Seqera account. The accessToken is added as above from the Seqera portal. There is no workspace name as it is a private Seqera account.

But I am getting a docker pull limit error when I run this pipeline for more than 60 samples within 6 hours.

Caused by:
Task failed to start - CannotPullImageManifestError: Error response from daemon: toomanyrequests: You have reached your unauthenticated pull rate limit. 
https://www.docker.com/increase-rate-limit

Is there any other piece of information I need to provide to the pipeline in order to login to the docker.io to provide Dockerhub pro-account access to the pipelines?

2

Hi @Sathiya_Manivannan ,

One quick question to double check. In your code block above, you wrote enabled = false for wave. Was that a typo or is this what you actually have set in your configuration. For Wave to be active and use the Dockerhub PAT that you added to Seqera, you need to activate Wave with enabled = true. Just want to make sure this is set correctly before potentially diving deeper.

Best,

Florian

1 Like