-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 1809 images support #2558
Comments
We do not support 1809 images yet. We have an issue when rebasing on 1809 image using @StefanScherer |
StefanScherer/rebase-docker-image#5 cc @ssbkang |
In the meantime you could use the image |
Is there a specific tag for chocolateyfest image?
|
No, just lastest. On my windows_2019_docker Vagrant box which was built some weeks ago I have the base image pulled and it works:
When I remove all the nanoserver base images and run it again
I ran the demo last Wednesday on some Azure VM's that also have the nanoserver image pre-pulled it also worked. Just run this command
and running the portainer should work afterwards. |
Ah, I understand now. The problem with such old Windows images from chocolateyfest use the original download link of the nanoserver image.
After Microsoft has withdrawn the ISO files and the Docker images they redeployed it later after some weeks. But it seems the download link has changed when you inspect the manifest of the current nanoserver image
As you can see the checksum and size is the same, but the foreign link to the Windows base image is a different one. Probably the old one gets an 404 or something that doesn't fit the sha256 sum. |
You need to rebuild your image and upload to docker hub? |
No I don't have to rebuild the image. I only have to push it again, the foreign link will be updated in the manifest. |
It should work now. |
@deviantony as a side comment. You can use Win Srv 1809 to build images for older versions too using native Docker tools. You can find guide and example for it from: https://github.com/olljanat/multi-win-version-aspnet |
Dear Developers, This could help till we get from portainer registry. Note: This suggestion is for hosting portainer on Win server 2019 (ver 10.0.17763.107) |
I just updated the rebase tool and tried it
I then can spin up the container on an Azure VM with Windows Server 2019 and Containers feature w/ Docker EE 18.09 installed:
|
@deviantony and what about agent image ? |
And how would it be in the case of the Portainer Agent in W2K19? (https://hub.docker.com/r/portainer/agent) |
Afaik, next version of Portainer will provide official support for Win Srv 2019. Be patient. Just side note. Win Srv 2019 introduced lot of new issues which why it cannot be consider to be production ready yet. Look: moby/moby#38498 |
@olljanat any ETA when the next portainer version will be released ?! thanks. |
Portainer 1.20.1 and Portainer agent 1.2.1 will be released this week. |
support win server(1809) and win10(1809)? |
Yes, we will try to publish 1809 images based on the updated version of the rebase-image-tool |
@deviantony I guess the rebase-image-tool does not transfer the manifest from mcr to docker hub for new image layers (eg. after each patch tuesday). So you may need the |
Thanks for the info @StefanScherer 👍 |
hi docker push ipaddress:5000/webapi:1.0.0 |
@hasan419 sorry but this is not a Docker support channel, you'd be better asking questions related to windows/docker inside a Docker support channel. |
FYI portainer agent version 1.2.1 has been released and should be compatible with Windows 1809. Portainer 1.20.1 coming soon. |
@deviantony thanks :), jumping on to it ... |
I try to installer the portainer agente usgin:
But i receive the following error in docker logs: ` goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: goroutine 1 [running]: Did I do something wrong? |
Going to investigate this one, keep you posted |
@mmgil can you try to run it as a standalone container ?
I wonder if it's an issue on Windows 1809 and/or if it's related to Swarm. |
@deviantony your command works for me, running the docker cli on my Mac I have to quote the backslashes
|
Haven't used the agent yet, I just created a single node swarm and ran this (without a custom network)
|
Yeah the agent must be part of an overlay to work in a Swarm but thanks for the input anyway ! I'll investigate the cause of the issue. |
Would you like me execute this command on a docker node without a swarm? |
@mmgil most probably that happens because code cannot find network card. |
This is the docker info in my environment:
|
@olljanat did you found on your try`s also the problem with overlay networks
It seems overlay networks created on docker manager are not being seen from windows worker nodes, My setup: All are running on docker engine 18.09.1 |
@mmgil 18.03.1-ee-5 is released before Win Srv 2019 so most probably it is not tested with it. Plz upgrade to 18.09.1. I can also see that your setup misses some Windows updates as .107 is not latest. @egzonzeneli that is most probably related to moby/moby#38484 which afaik is bug on Windows and will need update from Microsoft side. So probably is not possible to use Portainer agent inside of overlay network before that 😢 How ever it should be possible to Portainer it selves on Win Srv 2019. @deviantony we most probably need also add some checks to code so it will give some nice error message instead of just crashing. |
I've performed the update in the environment, this is the result of the docker info:
but, occurs the same error in portainer\agent using docker run --rm --network portainer_agent -e AGENT_CLUSTER_ADDR=tasks.portainer_agent -v \.\pipe\docker_engine:\.\pipe\docker_engine portainer/agent:
i'll try run a container with the image mcr.microsoft.com/windows/nanoserver:1809 in the network overlay portainer_agent to see if network is all right. |
@mmgil are you using some special configuration which disables IPv6, etc? I can see that Link-local IPv6 Address is missing from those pictures. I just tested on my Win 2019 lab machine that it exists on there. Currently Portainer agent is using second IP address from first vEthernet interface which it can find as normally first IP is link-local IPv6 and now it is failing on your env as there is only one IP. |
oooooh, That must be it. In fact I disabled the IPV6 of the template of the Virtual Machine in my environment. I will activate IPV6 in this environment and test again. |
AND... vooooia lá My Friends... It's working. You are the sacred Monsters of the Portainer and Docker. Thank you very much for your help and congratulations.
|
Good to know, still, we'll want to update the current IP retrieval algorithm to something that would be more stable. |
Portainer 1.20.1 is out and can be deployed on Windows 1809. Thanks to everyone for their contribution. |
Thank you! @deviantony Just a heads-up the latest manifest list looks different for linux as the previous ones.
(Maybe you need a |
@ssbkang could you have a look? |
@deviantony I just pushed new manifests with the missing annotations, and also updated our release pipeline.
Thanks so much for picking this up @StefanScherer, legend! 👍 |
Trying to run per documentation on Windows 2019 throws error below
The text was updated successfully, but these errors were encountered: