We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The dotnet framework installed is 4.7. I want to install dotnet framework 4.8 on top of the octo image.
If I setup a test image targeting FROM mcr.microsoft.com/windows/servercore:ltsc2019 it works fine.
FROM mcr.microsoft.com/windows/servercore:ltsc2019
However, targeting FROM octopusdeploy/tentacle just doesn't seem to install it.
FROM octopusdeploy/tentacle
I added these two lines to install it correctly on the test image
ADD https://go.microsoft.com/fwlink/?linkid=2088631 "C:/Downloads/ndp48-x86-x64-allos-enu.exe" RUN ["powershell", "-command", "C:/Downloads/ndp48-x86-x64-allos-enu.exe", "-ArgumentList", "/q", "/norestart"]
ADD https://go.microsoft.com/fwlink/?linkid=2088631 "C:/Downloads/ndp48-x86-x64-allos-enu.exe"
RUN ["powershell", "-command", "C:/Downloads/ndp48-x86-x64-allos-enu.exe", "-ArgumentList", "/q", "/norestart"]
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Team
What happened?
The dotnet framework installed is 4.7. I want to install dotnet framework 4.8 on top of the octo image.
If I setup a test image targeting
FROM mcr.microsoft.com/windows/servercore:ltsc2019
it works fine.However, targeting
FROM octopusdeploy/tentacle
just doesn't seem to install it.Reproduction
I added these two lines to install it correctly on the test image
ADD https://go.microsoft.com/fwlink/?linkid=2088631 "C:/Downloads/ndp48-x86-x64-allos-enu.exe"
RUN ["powershell", "-command", "C:/Downloads/ndp48-x86-x64-allos-enu.exe", "-ArgumentList", "/q", "/norestart"]
Error and Stacktrace
No response
More Information
No response
Workaround
No response
The text was updated successfully, but these errors were encountered: