Add MATLAB_UPDATE argument to dockerfile

[PVDecker1]

I would consider this an enhancement request.

There are cases where it is useful to test/troubleshoot code across release updates, but none of the dockerfiles have a means of installing a specific update of any given release.

It can be done fairly simply by adding a MATLAB_UPDATE argument, then appending it to MATLAB_RELEASE during the mpm call. That is what I do to accomplish update-specific MATLAB builds at least, although I would prefer TMW implement this behavior.

[michaelmcdonnellmw]

Hi @PVDecker1, thanks for raising this enhancement request, I will pass it on to the dev to to instigate

[josmartin]

@PVDecker1 Just want to make sure you are aware of the following syntax for mpm where you add Un to the end of the release argument to specify the release update you would like ...

$ ./mpm install --destination=`pwd` --release=R2024aU4 MATLAB
Installing with the following parameters:
--destination=/tmp/test-install
--doc=false
--release=R2024aU4
--products=MATLAB
---------------------------------------------
The following MathWorks Products are licensed under the The MathWorks, Inc. Software License
Agreement, available in the installation of the MathWorks Product or in the virtual machine image.
MATLAB

Products will be installed to: /tmp/test-install
Starting install
Finished install

[PVDecker1]

I am aware that mpm can do this directly, but the matlab-deps tags and mpm do not utilize the same nomenclature, as passing r2024aU2 to the dockerfile would not make it past the FROM statement. The same goes for OS specific installs, as I cannot pass r2024a-ubi since that succeeds at the FROM statement, but is ignored during the mpm call, unless the latter is by design.

[rebolloluis]

+1 to this. It took me a couple of hours of online research in forums, etc, to finally find a way to build a custom image for a specific MATLAB update for 2024a. Thank you @PVDecker1 for raising the issue and sharing how to workaround this.

I would love to be able to use it in the docker file as suggested in this answer years ago.

[rebolloluis]

FYI I opened a PR just to show others with the same issue how to implement this functionality in the Dockerfile.