Skip to content

Updated docker to 19.03.12 and golang to 1.13.12#9

Merged
StefanScherer merged 7 commits intoStefanScherer:masterfrom
carlitorendon:update-to-19.03.12
Jul 28, 2020
Merged

Updated docker to 19.03.12 and golang to 1.13.12#9
StefanScherer merged 7 commits intoStefanScherer:masterfrom
carlitorendon:update-to-19.03.12

Conversation

@carlitorendon
Copy link
Copy Markdown
Contributor

Used this tag to obtain versions:
https://github.com/docker/cli/releases/tag/v19.03.12

@StefanScherer
Copy link
Copy Markdown
Owner

Oh, there is no microsoft/windowsservercore:latest tag, MSFT has removed the latest tag long time ago. Maybe AppVeyor got it for convenience reasons. Should be ltsc2019 nowadays.

@carlitorendon
Copy link
Copy Markdown
Contributor Author

carlitorendon commented Jul 27, 2020

Oh, there is no microsoft/windowsservercore:latest tag, MSFT has removed the latest tag long time ago. Maybe AppVeyor got it for convenience reasons. Should be ltsc2019 nowadays.

Hello @StefanScherer thank you for pointing that out. After playing lottery with the windows host, it turned out to be ltsc2016.

Now the process is dying on this line:
RUN powershell iex(iwr -useb https://chocolatey.org/install.ps1)

claiming it can't validate the SSL connection to chocolatey.org... (I have seen that in places where some protection software running on the host puts itself in the middle to do some sort policing
on endpoints. I actually have seen this particular problem with chocolatey.org).

I tried to add a -SkipCertificateCheck flag just to realize it is only supported in PowerShell 7. Of course ltsc2016 is running stock 5.0 (where the flag is not allowed).

Any ideas 🤔?

…colatey (because it is failing due to a false positive SSL warning)
@StefanScherer
Copy link
Copy Markdown
Owner

Oh, indeed ltsc2016. Well that can be fixed by updating the AppVeyor image.

https://www.appveyor.com/docs/windows-images-software/#docker

In the appveyor.yml use Visual Studio 2019 which is installed on a Windows Server 2019. Docker has evolved a lot since Server 2016 came out, I encourage to use the newest OS available.

…respondingly made the docker file use Windows Long Term Service Channel (LTSC) 2019 as well.
@carlitorendon
Copy link
Copy Markdown
Contributor Author

Oh, indeed ltsc2016. Well that can be fixed by updating the AppVeyor image.

https://www.appveyor.com/docs/windows-images-software/#docker

In the appveyor.yml use Visual Studio 2019 which is installed on a Windows Server 2019. Docker has evolved a lot since Server 2016 came out, I encourage to use the newest OS available.

Hello @StefanScherer thank you for the tip! New to AppVeyor. It seems like it passed ok.

Copy link
Copy Markdown
Owner

@StefanScherer StefanScherer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks for updating the pipeline and bumping the version.

@StefanScherer StefanScherer merged commit 6432736 into StefanScherer:master Jul 28, 2020
@StefanScherer
Copy link
Copy Markdown
Owner

@carlitorendon a new github release is live. 😀

@carlitorendon
Copy link
Copy Markdown
Contributor Author

@carlitorendon a new github release is live. 😀

@StefanScherer thank you for pointing me in the right direction!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants