I was able to log in only once at the beginning, and only for a short period of time, since then after pushing the Log in button
I see a massage "Operation failed. Time out..."
Unexpectedly after pushing the Log in button like 20 times, I was able to log in again for a short period of time, and three minutes later, as you can see down below, container stopped working.

The creator of the image has advised me to ask the TP-Link forum, here is the original massage, "I would say that sounds like an application issue. I haven't seen anything like that related to it running in a container so your best bet is to report this on the TP-Link Forums and see if you can get traction with the team who has access to the code."

Configuration:
Bridge - Static IP 192.168.0.3

Image :
mbentley/omada-controller

Name :
omada-controller-1

Command :
/usr/bin/java -server -Xms128m -Xmx1024m -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+HeapDumpOnOutOfMemoryError -cp /opt/tplink/EAPController/lib/*: com.tplink.omada.start.OmadaLinuxMain

Entrypoint :
/entrypoint.sh

Console:

2021-04-07 17:56:56 [qtp1241529534-106] [WARN]-[HttpChannel.java:597] - /theme/img/svg/NavigationBarIconMore.svg
javax.servlet.ServletException: org.apache.shiro.session.UnknownSessionException: There is no session with id [e89319a3-19f3-40e6-a448-397be618c1e6]

Caused by: org.apache.shiro.session.UnknownSessionException: There is no session with id [e89319a3-19f3-40e6-a448-397be618c1e6]
at org.apache.shiro.session.mgt.eis.AbstractSessionDAO.readSession(AbstractSessionDAO.java:170) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.DefaultSessionManager.retrieveSessionFromDataSource(DefaultSessionManager.java:236) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.DefaultSessionManager.retrieveSession(DefaultSessionManager.java:222) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.AbstractValidatingSessionManager.doGetSession(AbstractValidatingSessionManager.java:118) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.AbstractNativeSessionManager.lookupSession(AbstractNativeSessionManager.java:148) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.AbstractNativeSessionManager.lookupRequiredSession(AbstractNativeSessionManager.java:152) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.AbstractNativeSessionManager.getAttribute(AbstractNativeSessionManager.java:249) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.mgt.DelegatingSession.getAttribute(DelegatingSession.java:141) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.session.ProxiedSession.getAttribute(ProxiedSession.java:121) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.subject.support.DelegatingSubject.getRunAsPrincipalsStack(DelegatingSubject.java:473) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.subject.support.DelegatingSubject.getPrincipals(DelegatingSubject.java:157) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.subject.support.DelegatingSubject.getPrincipal(DelegatingSubject.java:153) ~[shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getSubjectPrincipal(ShiroHttpServletRequest.java:96) ~[shiro-web-1.4.0.jar:1.4.0]
at org.apache.shiro.web.servlet.ShiroHttpServletRequest.getUserPrincipal(ShiroHttpServletRequest.java:112) ~[shiro-web-1.4.0.jar:1.4.0]
at org.springframework.web.servlet.FrameworkServlet.getUsernameForRequest(FrameworkServlet.java:1159) ~[spring-webmvc-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.publishRequestHandledEvent(FrameworkServlet.java:1144) ~[spring-webmvc-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1022) ~[spring-webmvc-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897) ~[spring-webmvc-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) ~[javax.servlet-api-3.1.0.jar:3.1.0]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) ~[spring-webmvc-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ~[javax.servlet-api-3.1.0.jar:3.1.0]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) ~[jetty-servlet-9.4.15.v20190215.jar:9.4.15.v20190215]
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) ~[jetty-servlet-9.4.15.v20190215.jar:9.4.15.v20190215]
at com.tplink.omada.web.filter.CacheControlFilter.doFilter(SourceFile:51) ~[omada-web-4.2.11.jar:?]
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) ~[jetty-servlet-9.4.15.v20190215.jar:9.4.15.v20190215]
at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61) ~[shiro-web-1.4.0.jar:1.4.0]
at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108) ~[shiro-web-1.4.0.jar:1.4.0]
at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137) ~[shiro-web-1.4.0.jar:1.4.0]
... 46 more
2021-04-07 17:57:41 [nioEventLoopGroup-6-1] [WARN]-[SourceFile:75] - device with ip /192.168.0.10:45700 pre connect manage channel exception: Adjusted frame length exceeds 1048576: 1195725860 - discarded
2021-04-07 17:57:41 [nioEventLoopGroup-9-1] [WARN]-[SourceFile:76] - null with ip /192.168.0.10:51484 adopt channel exception: Adjusted frame length exceeds 1048576: 1195725860 - discarded
2021-04-07 17:57:50 [nioEventLoopGroup-6-2] [WARN]-[SourceFile:75] - device with ip /192.168.0.10:45916 pre connect manage channel exception: Adjusted frame length exceeds 1048576: 1195725860 - discarded
2021-04-07 17:57:50 [nioEventLoopGroup-9-2] [WARN]-[SourceFile:76] - null with ip /192.168.0.10:51714 adopt channel exception: Adjusted frame length exceeds 1048576: 1195725860 - discarded
^C2021-04-07 17:59:59 [comm-pool-0] [WARN]-[SourceFile:135] - get InterruptedException while saving log.
ShutdownHook: service stopped.