Skip to content
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

Error when running under .NET 6.0.200 in a container #1521

Closed
mispencer opened this issue Feb 17, 2022 · 5 comments
Closed

Error when running under .NET 6.0.200 in a container #1521

mispencer opened this issue Feb 17, 2022 · 5 comments
Labels
Resolved-Duplicate This issue or pull request already exists

Comments

@mispencer
Copy link

We are running dotnet-format in a container (mcr.microsoft.com/dotnet/sdk:6.0). As of today, that tag was upgraded to .NET 6.0.200, and dotnet format started failing with the following error:

Could not load file or assembly 'Microsoft.CodeAnalysis.CSharp, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
Could not load file or assembly 'Microsoft.CodeAnalysis, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.

I creating a simple example here: https://github.com/mispencer/net6_0_200-docker-format-issue/blob/master/Dockerfile
The build-working target, referencing a direct image hash to the old 6.0.10x image, works.
The build-broken target, referencing mcr.microsoft.com/dotnet/sdk:6.0 tag and thus 6.0.200, fails with said error.

@ranma42
Copy link

ranma42 commented Feb 17, 2022

might be related to #1519

@Ekwy
Copy link

Ekwy commented Feb 24, 2022

My team landed on the same issue.

@WeihanLi
Copy link
Contributor

+1

@sungam3r
Copy link

sungam3r commented Mar 2, 2022

@JoeRobich
Copy link
Member

Closing as duplicate of #1519. See this comment for a workaround #1519 (comment)

@JoeRobich JoeRobich added the Resolved-Duplicate This issue or pull request already exists label Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolved-Duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

6 participants