# "no Docker image" for forked project

**URL:** <https://renku.discourse.group/t/no-docker-image-for-forked-project/534>\
**Category:** General\
**Created:** [28 January 2022 11:05 UTC](https://renku.discourse.group/t/no-docker-image-for-forked-project/534 "2022-01-28T11:05:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![andreas](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/andreas/32/8_2.png) [@andreas](https://renku.discourse.group/u/andreas)\
**Post date:** [30 January 2022 21:27 UTC](https://renku.discourse.group/t/no-docker-image-for-forked-project/534/4 "2022-01-30T21:27:00Z")

</div>

Have you looked at the option of [pinning an image](https://renku.discourse.group/t/how-to-pin-a-docker-image/240)? This would generally remove the need for an image build pipeline to run on the forked projects. For teaching use-cases this is often the way to go.

---

_[View the full topic](https://renku.discourse.group/t/no-docker-image-for-forked-project/534)._