3 ms·
>Of course we could use Docker, but then on Mac our dev process would be 3x slower. Doesn't devbox depend on Docker, though? I figure any performance losses fr
by nidnogg 4y ago
>Of course we could use Docker, but then on Mac our dev process would be 3x slower.
Doesn't devbox depend on Docker, though? I figure any performance losses from Docker would happen with this too.
- Aeolun 4y agoOnly for the build step (e.g. making a docker image). The dev step runs entirely on your machine. I got that from the README btw, no guarantees :)
- dloreto 4y agoThe dependency on Docker only exists for when you want to turn your shell into a container – but it's not otherwise used when you're just running a shell locally. When writing javascript there's often a desire to have "isomorphic" or "universal" applications. Write the code once and run it in _either_ the client or the _server_. Devbox is taking a similar approach to the development environment: declare it once, run it locally as a shell, and when you're ready, turn it into a container without having to re-declare it. It's only the latter functionality that has a Docker dependency.
- nidnogg 4y agoHmmm, I'll be keeping an eye on this one then!
- chupasaurus 4y agoIt's actually not since BuildKit could be run as a standalone daemon, and you can run the result via containerd which is a dependency of Docker. Might write a PR over the weekend(s).