windows-container

Windows Container swarm publish port and not access

ⅰ亾dé卋堺 提交于 2019-12-24 10:09:03
问题 I use windows container and try to create docker swarm ,I create three virtual machine use hyper-v , and each OS is windows server 2016.There machines ip is : windocker211 192.168.1.211 windocker212 192.168.1.212 windocker219 192.168.1.219 The docker swarm node is : PS C:\ConsoleZ> docker node ls ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS 4c0g0o0uognheugw4do1a1h7y windocker212 Ready Active bbxot0c8zijq7xw4lm86svgwp * windocker219 Ready Active Leader wftwpiqpqpbqfdvgenn787psj windocker211

Using Docker and Compose in Hyper-V with Windows Server 2016

前提是你 提交于 2019-12-24 08:37:29
问题 I currently have a Hyper-V Virtual machine whose guest OS is Microsoft Server 2016 I was able to install the Docker Service and use the command line to create a docker image I would like to try the same process out in Visual Studio using compose, but it looks like that will only work if the ToolBox is installed. I installed the Toolbox and when I build I get an error around the volume spec, I believe this is because the target OS is Linux. Since Windows Server 2016 is not compatible with

Unable to install windowsServerCore Container Image

徘徊边缘 提交于 2019-12-23 21:27:54
问题 I am trying to install windowsServercore images on my WIndows 2016 server using below command. Install-containerImage WindowsServerCore while running it got below error message. Install-ContainerOSImage : The term 'Install-ContainerOSImage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Found there is a work around from article https://social.msdn

Variable handling during windows docker build

陌路散爱 提交于 2019-12-21 20:17:22
问题 How can i define variables in the Dockerfile for a windows image so they are accessible in subsequent RUN statements? My test Dockerfile looks like this FROM microsoft/windowsservercore SHELL ["powershell", "-Command"] ARG viaArg=value ENV viaEnv="""value""" RUN $viaShell=\"value\" RUN echo """viaArg: $env:viaArg""" RUN echo """viaEnv: $env:viaEnv""" RUN echo """viaShell: $myusername""" RUN echo """viaShell+env: $env:viaShell""" when building the image via PS > docker build -t myImage . only

Can't find a good docker image for windows version 14393

拜拜、爱过 提交于 2019-12-11 17:47:58
问题 I am trying to setup a docker image for an mvc5 website to deploy to my service fabric Windows server 2016 with containers based cluster. It seems that every image with IIS configured is based on a different windows build than 14393, and when I deploy those to service fabric they fail to start on my windows servers. Am I missing something here? Does it matter what server the dockerfile runs on? So far is seems impossible to get a simple site up and running in a docker container on my service

Invalid volume specification trying to run portainer container

我的未来我决定 提交于 2019-12-11 17:32:35
问题 I'm trying to deploy portainer to my local docker. I'm running the Docker CE 18.0.6.0 version on Windows 10. I tried to follow the steps from these two pages: Portainer-Deployment Tutorial: Portainer for local Docker environments on Windows 10! But all the times I have tried to run the following command: docker run -d -p 9000:9000 --name portainer --restart always -v portainer_data:/data portainer/portainer -H tcp://10.0.75.1:2375 Docker responds always with the same message: Error response

Variable handling during windows docker build

萝らか妹 提交于 2019-12-04 14:09:24
How can i define variables in the Dockerfile for a windows image so they are accessible in subsequent RUN statements? My test Dockerfile looks like this FROM microsoft/windowsservercore SHELL ["powershell", "-Command"] ARG viaArg=value ENV viaEnv="""value""" RUN $viaShell=\"value\" RUN echo """viaArg: $env:viaArg""" RUN echo """viaEnv: $env:viaEnv""" RUN echo """viaShell: $myusername""" RUN echo """viaShell+env: $env:viaShell""" when building the image via PS > docker build -t myImage . only viaArg and viaEnv show (a) value. The first example here puts multiple commands in one line like RUN

HNS failed with error : The parameter is incorrect

℡╲_俬逩灬. 提交于 2019-12-04 11:26:56
问题 I am making a docker containerized application using visual studio 2017. When running docker through visual studio first, I got an error that "ERROR: client version 1.22 is too old". This error was resolved by updating docker compose to version 2.1 Below link contains further instruction about this specific error ERROR: client version 1.22 is too old After this error was resolved ,On Building docker now I get "HNS failed with error : The parameter is incorrect." From multiple github

HNS failed with error : The parameter is incorrect

落爺英雄遲暮 提交于 2019-12-03 06:14:18
I am making a docker containerized application using visual studio 2017. When running docker through visual studio first, I got an error that "ERROR: client version 1.22 is too old". This error was resolved by updating docker compose to version 2.1 Below link contains further instruction about this specific error ERROR: client version 1.22 is too old After this error was resolved ,On Building docker now I get "HNS failed with error : The parameter is incorrect." From multiple github discussion I have found that it is a windows network error. Is there a solution to this problem ? Should I down

Appending to PATH in a Windows Docker container

拈花ヽ惹草 提交于 2019-11-29 10:14:28
I need to append to the PATH within a Windows Docker container, and I've tried many permutations. ENV PATH=%PATH%;C:\\Foo\\bin ENV PATH=$PATH;C:\\Foo\\bin ENV PATH="%PATH%;C:\Foo\bin" ENV PATH="$PATH;C:\Foo\bin" RUN "set PATH=%PATH%;C:\Foo\bin" None of these work: they don't evaluate the preexisting PATH variable. What is the right syntax to append to the PATH? Can I even append to the PATH inside Docker? (I can on similar Linux containers) Unfortunately ENV won't work, because windows environment variable work a little differently than linux. more info As of now the only way to do this is