# Using an execution environment, unable to fetch into host volume

**URL:** <https://forum.ansible.com/t/using-an-execution-environment-unable-to-fetch-into-host-volume/44647>\
**Category:** Get Help\
**Tags:** ansible-navigator, ee, ansible-core\
**Created:** [October 8, 2025, 11:28pm UTC](https://forum.ansible.com/t/using-an-execution-environment-unable-to-fetch-into-host-volume/44647 "2025-10-08T23:28:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddimatos](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ddimatos/32/1040_2.png) [@ddimatos](https://forum.ansible.com/u/ddimatos)\
**Post date:** [October 8, 2025, 11:28pm UTC](https://forum.ansible.com/t/using-an-execution-environment-unable-to-fetch-into-host-volume/44647/1 "2025-10-08T23:28:09Z")

</div>

Hi there,  
Looking for any pointers that instructs the EE to write to a volume so I can access the `fetch`’d data.

In summary, the playbook runs just fine, I can `cat` the file I am fetching from within the playbook but it never ends up in the volume. Volume src is `/tmp/temp` and dest is `/tmp`, see below.

File ansible-navigator:

```auto
ansible-navigator:
  ansible:
    inventory:
      entries:
      - inventory.yml
  execution-environment:
    container-engine: podman
    volume-mounts:
      - src: /tmp/temp
        dest: /tmp
        options: "Z"
    enabled: true
    image: localhost/user/ibm-zos-ee
    pull:
      policy: never
  logging:
    level: debug

```

I have also run it with the volume options passed as well (below) and other variations:  
`ansible-navigator run test.yml -i inventory.yml -m stdout --eev /tmp/temp:/tmp/:rw,Z`

The only think that gets written into the volume is:

```auto
/tmp/temp $: pwd
/tmp/temp
/tmp/temp $: ls -laR
total 0
drwxrwxrwx@ 3 user wheel 96 Oct 7 22:49 .
drwxrwxrwt 13 root wheel 416 Oct 8 13:51 ..
drwxr-xr-x 2 user wheel 64 Oct 7 22:49 ibm-zos-ee

./ibm-zos-ee:
total 0
drwxr-xr-x 2 user wheel 64 Oct 7 22:49 .
drwxrwxrwx@ 3 user wheel 96 Oct 7 22:49 .

```

Playbook task is pretty simple:

```auto
    - name: Fetch another file
      ansible.builtin.fetch:
        src: /tmp/out.txt
        dest: /tmp/out.2.txt
        flat: true
      register: result

    - name: Cat out.2.txt
      vars:
        ansible_python_interpreter: /usr/bin/python3
      ansible.builtin.command:
         cmd: "cat /tmp/out.2.txt"
      register: result
      ignore_errors: true
      delegate_to: localhost

    - name: Print result.
      vars:
        ansible_python_interpreter: /usr/bin/python3
      ansible.builtin.debug:
        msg: "{{ result }}"
      ignore_errors: true

```

Result from cat shows the EE did fetch the file, (note the file only has the character `a` in it, very simple file) which you can see this `"stdout": "a",` below.

```auto
TASK [Print result.] ***********************************************************
ok: [zvm] => {
    "msg": {
        "changed": true,
        "cmd": [
            "cat",
            "/tmp/out.2.txt"
        ],
        "delta": "0:00:00.002201",
        "end": "2025-10-08 23:19:59.759859",
        "failed": false,
        "msg": "",
        "rc": 0,
        "start": "2025-10-08 23:19:59.757658",
        "stderr": "",
        "stderr_lines": [],
        "stdout": "a",
        "stdout_lines": [
            "a"
        ]
    }
}

```