You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2018. It is now read-only.
...the container starts up, 'scripts' appears as a folder in c:, but it's empty. The container can't see the contents of the folder. Again, this works just fine using the raw 'docker' call. Only when using the PowerShell module does this bug occur. Any ideas?
The text was updated successfully, but these errors were encountered:
Just a follow-up on this in case anyone else encounters the same thing. Mounting a host directory actually calls for use of the HostConfig class, not Config as indicated in some of the other forum posts here. Further, it's the 'Bind' property, not 'Volumes' that should be used to construct the mount. The follow revised script works and the directory is now visible from the container:
The following command executes successfully and I'm able to view my host directory "C:\temp" as "C:\scripts" on the container:
docker run -it -d --name festus -v c:\temp:c:\scripts core_usr_img
...but when performing the same action using the PowerShell module as follows...
...the container starts up, 'scripts' appears as a folder in c:, but it's empty. The container can't see the contents of the folder. Again, this works just fine using the raw 'docker' call. Only when using the PowerShell module does this bug occur. Any ideas?
The text was updated successfully, but these errors were encountered: