PATH issue Windows GUI - Docker

[pedgomgal1]

I am reporting a problem I am facing in the last version of BiaPy that did not occur in older ones. Windows paths are not recognised properly by Docker. I used Ubuntu like path in a previous biapy version (a month ago) and the input file bypass this issue. Now, the GUI does not allow to run the job at least I use the Windows path.

Attaching both .yaml files.

Old version with Ubuntu´s path that was functional several weeks ago. Now the GUI does not validate it just before running the job:
input20260205_105819.yaml

New version trying full Windows path:

input20260205_105819_modified.yaml

it brings the following error:

`#########################################################
NONE
#########################################################
Traceback (most recent call last):
File "docker\api\client.py", line 268, in _raise_for_status
File "requests\models.py", line 1021, in raise_for_status
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http+docker://localnpipe/v1.53/containers/011607c0c4ab54f0b0e1e19e76a1f946d09d8474013b663ba9f7965d453379ec/start

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "run_functions.py", line 787, in run
File "docker\models\containers.py", line 854, in run
File "docker\models\containers.py", line 405, in start
File "docker\utils\decorators.py", line 19, in wrapped
File "docker\api\container.py", line 1126, in start
File "docker\api\client.py", line 270, in _raise_for_status
File "docker\errors.py", line 39, in create_api_error_from_http_exception
docker.errors.APIError: 400 Client Error for http+docker://localnpipe/v1.53/containers/011607c0c4ab54f0b0e1e19e76a1f946d09d8474013b663ba9f7965d453379ec/start: Bad Request ("failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "--config": executable file not found in $PATH")`

I also tried to run a Bioimage zoo model (not a local checkpoint) and got the same error. I hope you can guide me to sort the issue. All the best.
Pedro

[pedgomgal1]

To add more info. I tried to run exactly the same job in a Ubuntu workstation using the GUI and worked.

[danifranco]

Are you using a network-mounted/mapped drive on Windows? Please try keeping YAML + data + output all on the same local drive (e.g. C:\...) and avoid UNC/mapped drives/OneDrive. Mixing drives can trigger Windows I/O/path issues.

[pedgomgal1]

Hi Dani, no. I am using a locally installed hardrive. When using all "windows paths" chosen by browsing through BiaPy GUI, it raises that error. In Linux GUI it works like a charm. Best