-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance issues on WSL #31
Comments
Hmm. Thanks for this report! I wonder if we want to support this as a separate image or set this as an optional behavior, since the common pattern on linux would be to mount a host directory into the container directly, and this image is geared toward such usage (e.g., matching uids on startup). |
Looking at the guidance you cited:
... I assume you were already following this advice and still seeing long build times? |
Sadly that advise cannot be followed when using WSL as the engine for Docker. I can script around it, but I would prefer not to because it would quite complicate things. I can fire up a PR and then you can comment on it. |
* Documentate limitations on WSL See #31 * Added alternative solution. Co-authored-by: Josh Mandel <jmandel@alum.mit.edu> --------- Co-authored-by: Lodewijk Sioen <lodewijk.sioen@infohos.be> Co-authored-by: Josh Mandel <jmandel@alum.mit.edu>
I'm using
ig-publisher-base
locally on a windows machine with Docker running on the WSL engine. A full publish takes more than 20 minutes. This is because there are serious performance issues in the interop between mounted windows filesystem and the Linux filesystem.Microsoft's guidance is to copy the files you want to work on over to the container filesystem.
I already did this on my own dockerfile and it reduced the build time from 20 minutes to 30 seconds.
If you're open to this, I can create a PR to contribute.
The text was updated successfully, but these errors were encountered: