Based on the build results on the Karsajobs backend (branch karsajobs), I see that all the source files are included in the image, and this creates big image size. These problems are such inconvenient for a student who has limited internet quota usage.
After finishing this learning course, we know that we build the binary and then run the image w/ the built binary. With that, why don't we create a multi-stage docker image build to reduce and minimize the size? Is there any concern from Dicoding to check the sources file in the image? I can try to create a PR to minimize the image using multi-stage image build. Let me know if I can do that. Thank you.
Based on the build results on the Karsajobs backend (branch karsajobs), I see that all the source files are included in the image, and this creates big image size. These problems are such inconvenient for a student who has limited internet quota usage.
After finishing this learning course, we know that we build the binary and then run the image w/ the built binary. With that, why don't we create a multi-stage docker image build to reduce and minimize the size? Is there any concern from Dicoding to check the sources file in the image? I can try to create a PR to minimize the image using multi-stage image build. Let me know if I can do that. Thank you.