I have volume binding set up mapping a few different paths to my Docker container. I have Docker plugin set up in Pycharm Pro and the container's interpreter set as my Python interpreter. I can deploy my python scripts using the docker interpreter without any trouble (in terms of packages and dependencies created on the docker image).
However, when deploying scripts and trying to access files stored on my local machine via volume bindings, it doesn't find them. When I open an interactive debug shell in pycharm and run os.path.exist, it returns True for the parent paths of the volume bindings (within the container) but returns False for any files or directories that are supposed to be mapped there from my local machine.
This is strange because the volume bindings are active, I have verified that in multiple ways:
I can see Pycharm's Docker tool window listing the bindings correctly
I can see the mapped files showing up in the container when checking from the terminal.
I can also open a terminal in my container and launch python shell and run os.path.exist this also returns True confirming that the directories are mapped and found under the paths I specified in my volume bindings.
Why can't I access my volume bindings when deploying python scripts through Pycharm's Docker interpreter - even though the scripts run fine otherwise?
Pycharm version: Pycharm Professional 2019.1.2
Docker version: 184.108.40.206
Local machine OS: macOS 10.13.4 High Sierra
Docker OS: Ubuntu 16.04