I receive License Manager Error 4402 when running matlab in a docker container in Linux

I fail to log in with my account and receive License Manager Error 4402.

I am building and running the docker in linux RedHat. I also run the same docker in other PC with Windows and it always start and run the script inside that docker without any problem.

This question has been asked previously: https://es.mathworks.com/matlabcentral/answers/2040781-why-do-i-receive-license-manager-error-4402-when-i-run-matlab-in-a-docker-container/?s_tid=ans_lp_feed_leaf

I have remove all the images and stopped containers in case the license has not been returned. But the same problem appears.

anybody know how to solve this error?

Thanks.

[Prabhakar]

Hi Could you please provide more information about 1. Which image are you running? 2. What is the command used to run the image 3. The steps you took to recieve this error? This information will help me reproduce your environment on my end

Thanks

[Álvaro Martin]

This is the dockerfile:

"""

ARG MATLAB_RELEASE=r2023b

# Specify the extra toolboxes to install into the image.

ARG ADDITIONAL_PRODUCTS="Industrial_Communication_Toolbox"

FROM mathworks/matlab:$MATLAB_RELEASE

# By default, the MATLAB container runs as user "matlab". To modify the MATLAB installation in the image, switch to root.

USER root

# Declare the global argument to use at the current build stage

ARG MATLAB_RELEASE

ARG ADDITIONAL_PRODUCTS

# Install mpm dependencies

RUN export DEBIAN_FRONTEND=noninteractive \

&& apt-get update \

&& apt-get install --no-install-recommends --yes \

wget \

unzip \

ca-certificates \

&& apt-get clean \

&& apt-get autoremove \

&& rm -rf /var/lib/apt/lists/*

# Run mpm to install MathWorks products and toolboxes into the existing MATLAB installation directory,

# and delete the mpm installation afterwards.

# Modify it by setting the ADDITIONAL_PRODUCTS defined above,

# e.g. ADDITIONAL_PRODUCTS="Statistics_and_Machine_Learning_Toolbox Parallel_Computing_Toolbox MATLAB_Coder".

# If mpm fails to install successfully then output the logfile to the terminal, otherwise cleanup.

WORKDIR /tmp

RUN wget -q https://www.mathworks.com/mpm/glnxa64/mpm \

&& chmod +x mpm \

&& EXISTING_MATLAB_LOCATION=$(dirname $(dirname $(readlink -f $(which matlab)))) \

&& ./mpm install \

--destination=${EXISTING_MATLAB_LOCATION} \

--release=${MATLAB_RELEASE} \

--products ${ADDITIONAL_PRODUCTS} \

|| (echo "MPM Installation Failure. See below for more information:" && cat /tmp/mathworks_root.log && false) \

&& rm -f mpm /tmp/mathworks_root.log

ENV MW_DDUX_FORCE_ENABLE=true MW_CONTEXT_TAGS=$MW_CONTEXT_TAGS,MATLAB:TOOLBOXES:DOCKERFILE:V1

# Now that the installation is complete, switch back to user "matlab"

USER matlab

# Set the working directory to /app

WORKDIR /home/app/

# Copy the MATLAB code to the container

COPY app .

# Execute the script to install addons when the container starts

CMD ["matlab", "-r", "publishMqtt"]

"""

As you can see, it is the r2023b version.

These are the steps i took to build the image and run the container:

# 1. sudo docker build -t matlab-river-mqtt .

# 2. sudo docker run -it matlab-river-mqtt

As i am using an academic license, SSO is not available, so I have to write my matwhorks account email adress and follow these steps:

[Prabhakar]

Thank you Alvaro!

This is very useful, I'll circle back with more after looking closer.

[Álvaro Martin]

Thank you so much Prabhakar!

[Prabhakar]

Alvaro, I've created a tech support service request on your behalf with MathWorks Technical Support.

They should be reaching out to you via email.

Given that this issue might take a while to solve, the tech support escalation should provide a nice way for you to query about updates.

In the mean time if I have any more updates, I'll be sure to update this post as well.

[Prabhakar]

@Álvaro Martin, just to let you know we are still investigating the issue, and attempting to develop workarounds for it, if not a real fix.

[Prabhakar]

Dear @Álvaro Martin, a fix for this issue should be shipped in a future update to R2023b. Unfortunately, there are no other workarounds that I can share at this point in time.

Answer 1

[Prabhakar]

Dear @Álvaro Martin

R2023b Update 6 has been updated to fix this issue.

Kindly update this thread if using R2023b Update 6 does not resolve the issue for you.

Thank you for your patience!