# Looking for Help with Docker image versions in Nextflow pipeline!

**URL:** https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221
**Category:** Ask for help
**Created:** [June 25, 2025, 9:32am UTC](https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221 "2025-06-25T09:32:34Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![marcossandrew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/marcossandrew/32/1427_2.png) [@marcossandrew](https://community.seqera.io/u/marcossandrew)
#### Post date: [June 25, 2025, 9:32am UTC](https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221/1 "2025-06-25T09:32:34Z")

</div>

Hi all,

I am currently working on a Nextflow pipeline to process RNA-seq data and I am running into an issue with Docker image versions. Specifically., I have defined containers in my process blocks.., but I am not sure how to pin them properly so the pipeline is reproducible across environments.

I am using nf-core’s recommended practices.., but I would like to understand:

Is it better to pin image versions in the nextflow.config or directly in the process definition: ??

How do I handle cases where a tool doesn’t offer versioned tags on Docker Hub: ??

Are there any tools or workflows in the Seqera ecosystem that help track or validate container usage: ??

Would really appreciate any pointers, examples, or best practices from folks who have handled this before. I have also gone through this resource [https://seqera.io/blog/docker-for-dunces-nextflow-for-nunces/](https://seqera.io/blog/docker-for-dunces-nextflow-for-nunces/)  
[sql training in mumbai](https://www.igmguru.com/microsoft-training/microsoft-sql-training-in-mumbai)  
but couldn’t find enough help.

Thanks in advance!

Marcos

---

<div class="post-metadata">

### Author: ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://community.seqera.io/u/discourse_ai_spam)
#### Post date: [June 25, 2025, 9:32am UTC](https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221/2 "2025-06-25T09:32:37Z")

</div>



---

<div class="post-metadata">

### Author: ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)
#### Post date: [June 26, 2025, 2:34pm UTC](https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221/3 "2025-06-26T14:34:36Z")

</div>



---

<div class="post-metadata">

### Author: ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)
#### Post date: [June 26, 2025, 2:37pm UTC](https://community.seqera.io/t/looking-for-help-with-docker-image-versions-in-nextflow-pipeline/2221/4 "2025-06-26T14:37:27Z")

</div>

> [@marcossandrew](#):
>
> Is it better to pin image versions in the nextflow.config or directly in the process definition: ??

I prefer to pin container image information in the process block as it makes it more modular.

> [@marcossandrew](#):
>
> How do I handle cases where a tool doesn’t offer versioned tags on Docker Hub: ??

I recommend you use [Seqera Containers](https://seqera.io/containers/), that offers [benefits when compared to DockerHub](https://seqera.io/blog/introducing-seqera-pipelines-containers/).

> [@marcossandrew](#):
>
> Are there any tools or workflows in the Seqera ecosystem that help track or validate container usage: ??

Seqera Containers 😉