# Use pixi (in-repo conda envs) as a light execution environment

**URL:** <https://forum.ansible.com/t/use-pixi-in-repo-conda-envs-as-a-light-execution-environment/44463>\
**Category:** Get Help\
**Tags:** ee\
**Created:** [September 11, 2025, 11:00am UTC](https://forum.ansible.com/t/use-pixi-in-repo-conda-envs-as-a-light-execution-environment/44463 "2025-09-11T11:00:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gzm55](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gzm55/32/9405_2.png) [@gzm55](https://forum.ansible.com/u/gzm55)\
**Post date:** [September 11, 2025, 11:00am UTC](https://forum.ansible.com/t/use-pixi-in-repo-conda-envs-as-a-light-execution-environment/44463/1 "2025-09-11T11:00:21Z")

</div>

Recently, i found the [pixi](https://pixi.sh/latest/) tool, which is a in-repo conda environments management tool.

The `pixi.toml` work like a light dockerfile with all the controller dependencies pinned in the `pixi.lock` file. The tool can install conda/pip packages into a in-repo conda env. After the repo is cloned, one can run `pixi run ansible-playbook ...` , the required packages or event the collections can be installed on the fly.

Is anyone also use this execution environment pattern?