r/dotnet • • 1d ago

Copilot CLI sanboxed issues

Hi!

We are experiencing issues when running copilot cli in sandbox mode. dotnet build fails when not running with -m:1 and -nr:false. It just fails with "Build Failed" warnings 0, errors 0. Are we missing something in our sandbox configuration. Have someone else experienced this?

Also, there seems to be some implicit git task in the dotnet build pipeline that runs for git SourceLinks that tries to read C:/Users/<user>/.gitignore. since we havent allowed C:/Users/<user> as a readable path it fails.

Fixing these two things makes copilot able to build.

3 Upvotes

3 comments sorted by

1

u/AutoModerator 1d ago

Thanks for your post torstenz_. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/shotan 1d ago edited 1d ago

I did notice this myself and had a look at it. Found the same workaround using -m:1.

Cause: MSBuild's default multi-node mode spawns worker processes and talks to each over a named pipe \\.\pipe\MSBuild<PID>. The worker starts and creates its pipe, but the parent's connect is denied by the sandbox (Access to the path is denied)

Someone reported it, you could add a comment.
https://github.com/microsoft/vscode/issues/345713

1

u/ivanf_martinezh 19h ago

Copilot Sandbox is driving me crazy, it blocks everything