4 ms·
Why not just have a shared volume for your dependencies? That way nothing needs to rebuild. Then just have a different Docker-compose config for prod
by austinpena 6y ago
Why not just have a shared volume for your dependencies? That way nothing needs to rebuild.
Then just have a different Docker-compose config for prod
- gravypod 6y agoThe main reasons are: 1. My applications have no dynamic "linking" 2. The containers are distroless 3. Services can be built independently 4. I run the same exact sha in dev/staging/prod To do what you're suggesting would require giving up one of my features which for me is not worth the trade off of a one-time setup 40min build of 20+ services (~2min/service). The last time I paid that 40min cost was ~2 months ago when I reformatted my hard drive. The better solution for me is looking into a build system that can support my different language and tooling choices which happens to be things like Blaze (Bazel/Pants/Buck/Please).