Paket restore hangs when used with docker build #3123

Activity

1. forki commented on Mar 17, 2018

   

   forki

   on Mar 17, 2018 via email

   Member

   More actions

   Yeah it's a long known issue. We have no idea what it's causing. Jack Mott <notifications@github.com> 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_> .
2. jackmott commented on Mar 17, 2018

   

   jackmott

   on Mar 17, 2018

   Author

   More actions

   @forki any workarounds?
3. forki commented on Mar 18, 2018

   

   forki

   on Mar 18, 2018 via email

   Member

   More actions

   Nope. I think it's a mono bug. Jack Mott <notifications@github.com> 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_> .
4. matthid commented on Mar 18, 2018

   

   matthid

   on Mar 18, 2018

   Member

   More actions

   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.
   Maybe some http request doesn’t timeout correctly. Or some user message pops up on the ci for some reason...
5. zakaluka

   added 2 commits that reference this issue on Jun 23, 2018

   Trying to get around fsprojects/Paket#3123 , attempt 1

   3c75bf8

   Undid fix for fsprojects/Paket#3123

   8e48a55
6. atadi96 commented on Feb 21, 2019

   

   atadi96

   on Feb 21, 2019

   More actions

   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.
7. forki commented on Feb 22, 2019

   

   forki

   on Feb 22, 2019

   Member

   More actions

   Sorry we still don't know what's going wrong here
8. ajuch commented on Nov 26, 2019

   

   ajuch

   on Nov 26, 2019

   More actions

   I'm having the same behavior with a .net core 3.0 sdk docker image.

   paket.dependencies:

   source https://api.nuget.org/v3/index.json
   
   storage: none
   framework: netcore3.0, netstandard2.0, netstandard2.1
   nuget canopy
   nuget Selenium.WebDriver.ChromeDriver
   

   Dockerfile:

   FROM mcr.microsoft.com/dotnet/core/sdk:3.0 AS build-env
   COPY . ./
   RUN dotnet tool restore
   RUN dotnet paket restore -v
   

   It hangs at:

   Step 5/11 : RUN dotnet paket restore -v
    ---> Running in ace15e1382a0
   Paket version 5.236.6
   found: /paket.dependencies
    - /.paket/Paket.Restore.targets already up-to-date
   Parsing /paket.dependencies
   

   So I don't think it's a mono issue...
9. forki commented on Nov 26, 2019

   

   forki

   on Nov 26, 2019

   Member

   More actions

   @ajuch cool thanks for the repro. I can actually reproduce it now
10. forki commented on Nov 26, 2019

    

    forki

    on Nov 26, 2019

    Member

    More actions

    I added crazy amout of logging and here we are:

    
11. forki commented on Nov 26, 2019

    

    forki

    on Nov 26, 2019

    Member

    More actions

    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?
12. forki

    added a commit that references this issue on Nov 26, 2019

    Exclude top-level linux folders - Fixes #3123

    This issue will close once commit b4baa00 is merged into the 'master' branch.

    b4baa00
13. forki commented on Nov 26, 2019

    

    forki

    on Nov 26, 2019

    Member

    More actions

    this is fixed in 5.238. thanks for the repro
14. forki

    closed this as completedin b4baa00on Nov 26, 2019
15. ajuch commented on Nov 26, 2019

    

    ajuch

    on Nov 26, 2019

    More actions

    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 strace dotnet paket restore.

    But it doesn't matter, now it works like a charm!
16. forki commented on Nov 26, 2019

    

    forki

    on Nov 26, 2019 via email

    Member

    More actions

    I added that additional tracing in intermediate releases to understand the bug. Andreas Juch <notifications@github.com> 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> .