Paket restore hangs when used with docker build #3123
Comments
|
Yeah it's a long known issue. We have no idea what it's causing.
Jack Mott <[email protected]> schrieb am Sa., 17. März 2018, 22:01:
… Description
paket restore hangs on my project when used in a docker build. It runs
very quickly when I run it outside of a docker build. While hung the mono
process is pegging 1 core. The last output of paket restore --verbose is
"parsing paket.dependencies"
Repro steps
paket.dependencies:
framework >= net45
nuget DotLiquid
nuget FSharp.Data
nuget FsSql
nuget MathNet.Numerics.FSharp
nuget Newtonsoft.Json
nuget Npgsql = 3.1
nuget Octokit
nuget SQLProvider
nuget Suave >= 2.3.0-beta3
nuget Suave.DotLiquid >= 2.3.0-beta3
nuget Suave.Experimental >= 2.3.0-beta3
Dockerfile:
FROM fsharp:latest
ADD . /
WORKDIR /
RUN mono .paket/paket.bootstrapper.exe
RUN mono .paket/paket.exe restore --verbose
RUN ./build.sh
ENTRYPOINT ["mono","/root/AlphaFront/bin/Release/AlphaFront.exe"]
I am running docker build with a private github repo as the context
The repo is private so I am sorry I cannot provide it.
Expected behavior
paket should work
Actual behavior
paket hangs and pegs a cpu core
Known workarounds
none
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3123>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNKGYgnmFB4ZKONef-CR7Q-Y8Nptoks5tfXnDgaJpZM4Su9p_>
.
|
|
@forki any workarounds? |
|
Nope. I think it's a mono bug.
Jack Mott <[email protected]> schrieb am Sa., 17. März 2018, 23:11:
… @forki <https://github.com/forki> any workarounds?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNJn2omyMh9DKNTr9JF-oN42a1nNTks5tfYn6gaJpZM4Su9p_>
.
|
|
As long as we don’t know how to reproduce or ge it into a debugger be accident. There is not much we can do. |
|
This is rendering me unable to create a repro for an issue with FAKE 5. What can I do in this case? Sorry if this in not the right place to ask but I'm lost. I've also found that paket restore does not hang when called in a gitlab-runner instance with docker runner. |
|
Sorry we still don't know what's going wrong here |
|
I'm having the same behavior with a .net core 3.0 sdk docker image. paket.dependencies: Dockerfile: It hangs at: So I don't think it's a mono issue... |
|
@ajuch cool thanks for the repro. I can actually reproduce it now |
|
I added crazy amout of logging and here we are:
|
|
so the problem is in https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/PaketConfigFiles/ProjectFile.fs#L1906 we are scanning all subfolders but inside the docker main folder we seem to run into an issue that we scan the whole file system. So what can we do? |
|
this is fixed in 5.238. thanks for the repro |
|
Thank you @forki! It works! Ah, I see what I did wrong... I should have put my app into a directory... But the funny thing is that I didn't see the recursive crawling when running But it doesn't matter, now it works like a charm! |
|
I added that additional tracing in intermediate releases to understand the
bug.
Andreas Juch <[email protected]> schrieb am Di., 26. Nov. 2019,
15:30:
… Thank you @forki <https://github.com/forki>! It works!
Ah, I see what I did wrong... I should have put my app into a directory...
But the funny thing is that I didn't see the recursive crawling when
running strace dotnet paket restore.
But it doesn't matter, now it works like a charm!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#3123?email_source=notifications&email_token=AAAOANFFTJMXBGHKNPJU3BLQVUXIHA5CNFSM4EV33J72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFGGLSY#issuecomment-558654923>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOANDT2IQNH7ODEO3T433QVUXIHANCNFSM4EV33J7Q>
.
|
Description
paket restore hangs on my project when used in a docker build. It runs very quickly when I run it outside of a docker build. While hung the mono process is pegging 1 core. The last output of paket restore --verbose is "parsing paket.dependencies"
Repro steps
paket.dependencies:
Dockerfile:
I am running docker build with a private github repo as the context
The repo is private so I am sorry I cannot provide it.
Expected behavior
paket should work
Actual behavior
paket hangs and pegs a cpu core
Known workarounds
none
The text was updated successfully, but these errors were encountered: