# ansible version within execution environment

**URL:** <https://forum.ansible.com/t/ansible-version-within-execution-environment/37344>\
**Category:** AWX Project\
**Tags:** ee\
**Created:** [November 14, 2022, 1:52pm UTC](https://forum.ansible.com/t/ansible-version-within-execution-environment/37344 "2022-11-14T13:52:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gregory\_Storme](https://avatars.discourse-cdn.com/v4/letter/g/46a35a/32.png) [@Gregory\_Storme](https://forum.ansible.com/u/Gregory_Storme)\
**Post date:** [November 14, 2022, 1:52pm UTC](https://forum.ansible.com/t/ansible-version-within-execution-environment/37344/1 "2022-11-14T13:52:56Z")

</div>

Hi,

Is it ok/safe to upgrade ansible-core in the “additional\_build\_steps” of ansible-builder to a higher branch than the used EE\_BASE\_IMAGE version?

Example:

build\_arg\_defaults:  
EE\_BASE\_IMAGE: ‘[quay.io/ansible/ansible-runner:stable-2.12-latest](http://quay.io/ansible/ansible-runner:stable-2.12-latest)’

additional\_build\_steps:  
prepend: |  
RUN pip3 install --upgrade ansible-core==2.13.6

Or is there a better way?  
Asking since there are no ansible-runner images available for ansible-core 2.13.

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [November 16, 2022, 7:41pm UTC](https://forum.ansible.com/t/ansible-version-within-execution-environment/37344/2 "2022-11-16T19:41:49Z")

</div>

This should be ok to try, let us know if you run into any issues.

-The AWX Team