4 ms·
This is a cool project and yay nix, but: > Inside a container the file system is very slow Because you are not using "a container". You are using a container
by justinsaccount 4y ago
This is a cool project and yay nix, but:
> Inside a container the file system is very slow
Because you are not using "a container".
You are using a container that happens to be running in a linux VM on your OS X laptop. It's not the containers fault, it's the entire virtual machine that you are running because you're trying to run technology built on top of one operating system while running a completely different one.
- endorphine 4y agoThis. Put another way: it's slow only because you're on macOS and not on Linux.
- dloreto 4y agoTotally fair.
- neop1x 4y agoThat's why Linux needs more love. I find it sad that many people use Docker, but the majority of them run Linux in a VM inside an expensive proprietary platform to do so, sometimes without even realizing it. Meanwhile, the Linux desktop ecosystem is deteriorating and should be used more and receive more financial support.
- throwaway892238 4y agoOverlay copy-on-write filesystems are slow. I think most container runtimes use them.
- baq 4y agocompared to full-VMs-pretending-to-be-containers everything is fast. it seems like everybody here is using Macs for development to the point that if you don't say you aren't, you are assumed to be on a mac. Windows with WSL2 is actually pleasant to use, I can recommend trying it out. while WSL2 is a VM technically, the level of integration makes it basically native (if you use the VM disk for your workspace, which you should.)
- justinsaccount 4y ago> if you use the VM disk for your workspace, which you should. Yep, if you try to build something that is stored on /mnt/c you'll have the same horrible performance.
- justinsaccount 4y agoIt's not the COW filesystem that is slow, it's bind mounting the host filesystem into the VM. This ends up using something like 9p or sshfs.