• desmaraisp@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    You can cap the amount of cpu/memory docker is allowed to use. That helps a lot for those issues in my experience, although it still takes somewhat beefy machines to run docker in wsl

    • qwop@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      When it happens docker+wsl become completely unresponsive anyway though. Stopping containers fails, after closing docker desktop wsl.exe --shutdown still doesn’t work, only thing I’ve managed to stop the CPU usage is killing a bunch of things through task manager. (IIRC I tried setting a cap while trying the hyper-v backend to see if it was a wsl specific problem, but it didn’t help, can’t fully remember though).

      This is the issue that I think was closest to what I was seeing https://github.com/docker/for-win/issues/12968

      My workaround has been to start using GitHub codespaces for most dev stuff, it’s worked quite nicely for the things I’m working on at the moment.