I have a container that has several volumes mapped to local folders. The volumes mount correctly and I can explore the local files through a bash into the container. All of these volumes can write to the local folders and I’ve successfully viewed logs and other files that the container created in the local folders. However, the container refuses to use the local files for any function within the container. All functions that search for these files return file-not-found errors, but have no problem writing logs and other output at the same time.
The overall effect is as if there is only one- communication direction … from the container to the local folders, but not the other way around. The local volumes are shared via Docker Desktop. It seems like this would be some kind of permissions issue, but I can’t determine what permissions would cause write-only to the local volume. There doesn’t appear to be any permissions issues within the container and with Docker Desktop allowing the Windows side, where would I go next to resolve the issue?