# Refresh pipeline runner image

**URL:** <https://community.okteto.com/t/refresh-pipeline-runner-image/1052>\
**Category:** Not sure?\
**Created:** [September 11, 2023, 11:41am UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052 "2023-09-11T11:41:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark90](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mark90/32/406_2.png) [@Mark90](https://community.okteto.com/u/Mark90)\
**Post date:** [September 11, 2023, 11:41am UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052/1 "2023-09-11T11:41:09Z")

</div>

Hi,

We are using a custom image for the pipeline runner as described here [Okteto Manifest | Okteto Documentation](https://www.okteto.com/docs/reference/manifest/#deploy-remotely)

We have now made a new version of this image, tagged “latest”, but we don’t know how to make the pipeline pull this new version.

The output in our pipeline is:

> Container image “/public-build-containers/okteto-pipeline-runner:latest” already present on machine

It makes sense that it reuses the cached image by default, to save time. But how can we make it pull the image, or is it possible to remove the cached image manually some way?

Kind regards,  
Mark

---

<div class="post-metadata">

**Author:** ![maroshii](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/maroshii/32/12_2.png) [@maroshii](https://community.okteto.com/u/maroshii)\
**Post date:** [September 11, 2023, 12:11pm UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052/2 "2023-09-11T12:11:11Z")

</div>

Hi @Mark90!

Okteto uses the pullPolicy defined in your helm installation. This is the default:

```auto
pullPolicy: IfNotPresent

```

You could change that to `Always` and it will fix it but it would have some performance implications since it will all pull images every time and no longer use the cache (not only for the installer).

Another option is to use a different images tag to take full advantage of the cache, for eg: `okteto-pipeline-runner:${GIT_SHA}` and change the tag every time there’s a change in the image. This is the recommended approach.

Hope that help!

Francisco

---

<div class="post-metadata">

**Author:** ![Mark90](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mark90/32/406_2.png) [@Mark90](https://community.okteto.com/u/Mark90)\
**Post date:** [September 11, 2023, 12:22pm UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052/3 "2023-09-11T12:22:12Z")

</div>

Hi Fransico,

Thanks for the quick reply!

The “Always” solution indeed sounds less favorable.

We’ve used the approach of changing the image tag, this works. It does require upgrading the okteto Helm manifest, but these changes are rare anyway so this will work for us.

Thank you!

Mark

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/okteto/original/1X/d4425507982f2cd3c24ec2204fe635243d361741.png) [@system](https://community.okteto.com/u/system)\
**Post date:** [October 21, 2025, 10:24am UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052/4 "2025-10-21T10:24:23Z")

</div>

Unlisted on October 21, 2025, 10:24am UTC



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/okteto/original/1X/d4425507982f2cd3c24ec2204fe635243d361741.png) [@system](https://community.okteto.com/u/system)\
**Post date:** [October 21, 2025, 12:37pm UTC](https://community.okteto.com/t/refresh-pipeline-runner-image/1052/5 "2025-10-21T12:37:58Z")

</div>

Listed on October 21, 2025, 12:37pm UTC


