Docker remote host: OCI runtime exec failed: exec failed: unable to start container process: chdir to cwd

edit

I have tried setting WORKDIR, but I don't think that's the issue here. Note that Wing is logging ['docker', 'exec', '-w', '/home/rutherford'], so I think the bad path is coming from wing. Also note that the docker image works fine (I am able to exec to it myself).

This probably indicates that you don't have a an entry to map /home/rutherford to /app or whatever it's supposed to be on the container. This is done with File Mappings under the General tab of the container configuration in Wing.

I was surprised we send -w but now I see that we do and it's sending the configured debug environment's run directory passed through the container file mapping, so it does look like that's the issue and adding an entry for /home/rutherford -> /app or similar should solve it. Please let me know if not.

I don't have an entry to map /home/rutherford into the container, but I also don't want it to be mapped! Can I not use a container without mapping any directories into it? In this case the code I want to use is already in the container.

How are the files edited? Wing's container support assumes files are mapped from somewhere on the host into the container. It then maps the container-side locations back to the host-side locations so it can show the file that can actually be edited on the local host. It doesn't try to edit files on the container because very often the container is short-lived and you would lose you edits.

If the container is being used more like a remote host that you can ssh into then you may just want to treat it that way instead in Wing, as described in https://wingware.com/doc/howtos/remote-…

BTW you could set the initial directory to a different value from Edit Environment in the Python Shell's Options menu but that will reject anything that doesn't exist on the host so this is probably not the right approach and not useful.

I was actually just trying to use Wing to view (and maybe debug) the files in the container. I had no plans to edit them in the short term.

But I think this answers my question. My initial directory is set to default, which the documentation suggests is ${WING:PROJECT_DIR}. Perhaps, as the project dir does not exist in the container, Wing falls back to ~ as the initial directory? This suggests that it would work as I expect if I could set Wing's initial directory to be the containers WORKDIR. However, when I am using a container environment, the initial directory option is greyed out.