Dotnet restore fails for container running on Linux, but succeeds on Windows.
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I have docker file with build process:
FROM mcr.microsoft.com/dotnet/sdk:3.1-buster as build
WORKDIR /Repo
COPY . .
RUN dotnet tool restore -v diag
RUN dotnet restore src -v diag
RUN dotnet build --no-restore -c Release -v diag src
RUN dotnet paket pack --interproject-references keep-major ../out
This works on Windows, but fails on Linux: (and in GitLab pipeline)
cloudflare-fsharp-api-package/.paket/Paket.Restore.targets(171,5): error MSB3073: The command "mono --runtime=v4.0.30319 "/builds/migamake/migamake-hurl/cloudflare-fsharp-api-package/.paket/paket.exe" restore" exited with code 127.
I have no idea how host can affect MSBuild running within docker container.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Docker build commands, especially dotnet tool restore and dotnet restore src, in the mcr.microsoft.com/dotnet/sdk:3.1-buster image. Inspect .paket/Paket.Restore.targets at line 171 and the reported paket.exe invocation; done means identifying why the Linux container exits with code 127 while the Windows build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, fsharp, gitlab
- Domain
- build-system, devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100