Hi, I am trying to bind docker volumes to my docker container after connecting to New_PSSession by running the following command
#Wait until PSSession is available
while ($true)
{
$p = New-PSSession $publicDNS -Credential $creds 2>$null
if ($p -ne $null)
{
break
}
"$(Get-Date) Waiting for remote PS connection"
Sleep -Seconds 10
}
Invoke-Command -Session $r {docker login --username=xxxx --password=xxxx}
Invoke-Command -Session $r {docker volume create volume01}
Invoke-Command -Session $r {docker pull xxx/my_repo:Testing}
Invoke-Command -Session $r {docker images}
Invoke-Command -Session $r { docker run --name test01 -it -v c:\programdata\docker\volumes\volume01:c:\volume01 xxxx/my_repo:Accessibility cmd}
i get shown the below error
the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'
+ CategoryInfo : NotSpecified: (the input devic...d with 'winpty':String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
+ PSComputerName : ec2-52-28-216-45.eu-central-1.compute.amazonaws.com
OS Version- windows Server 2016
Docker version:
PS C:> docker version
Client:
Version: 17.03.1-ee-3
API version: 1.27
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64
Server:
Version: 17.03.1-ee-3
API version: 1.27 (minimum version 1.24)
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64
Experimental: false
PS C:\>
I run docker “natively” from a Windows server 2016 with a Windows container, there is no intermediate VM (no docker machine) in between and no docker toolbox, so the “host” is the actual Windows Server that I run docker on. i’m able to do that on my local machine. In an automated way it isn’t working.
how would i fix this winpty issue?
Any advise on this would be helpful. Thanks in advance.