Update Dockerfile to Multi-Stage

[multi-stager]

Hi,

Thanks for maintaining mudslide. I represent a research group investigating multi-stage builds. We recently refactored your Dockerfile to a multi-stage Dockerfile and found that it brings the following benefits:

✅ Reduced final image size (from 1079MB to 447MB)
✅ Minimized image vulnerabilities (verified via Trivy, from 202 to 105)

We hope this small improvement to the Dockerfile will be useful to you :)

Thanks,

[robvanderleek]

Hi 👋

Thanks for the contribution, this is a nice improvement.

I needed to move one of the environment variables from the build stage to the runtime stage in order to prevent behavior regression.
Also, I removed the comments and named the second stage "runtime" (but this is just a personal preference.)

Do you have a bit more background on your research group? The multi-stager account looks very anonymous.

KR, Rob

[multi-stager]

@robvanderleek Hi Rob,

I'm glad to hear that you found our contribution valuable.

The reason for using an anonymous account for our PR is the double-blind restrictions in the submission process of conferences. We look forward to sharing more details once the anonymity period is over.

Thank you once again for your feedback. :)

Best regards,

[robvanderleek]

The reason for using an anonymous account for our PR is the double-blind restrictions in the submission process of conferences. We look forward to sharing more details once the anonymity period is over.

I see. PRs from an anonymous account are treated with a lot of suspicion by maintainers, be aware.

I've merged the PR, thanks again and good luck with the research 👍

[multi-stager]

I see. PRs from an anonymous account are treated with a lot of suspicion by maintainers, be aware.

I've merged the PR, thanks again and good luck with the research 👍

Thank you so much!