Parallels Tools Update breaks MYSQL in Docker setting date to year 2120

M3 MacBook Pro
macOS 26.0.1
Parallels Desktop
Version 26.1.1 Pro Edition
Ubuntu with Rosetta to run Docker

Title says it all. Working docker, system time on Ubuntu and in macOS are correct
Updated on 9/30
When doing a Docker Run, it dies when starting MYSQL, it says the date is too far in the future.
I pulled up a backup image from the 29th and Docker ran and MSQL had no issue.
I updated Parallels tools, this error returned.
I did this a few times. My current solution is to NOT update Parallels Tools and just continue working.

MYSQL Logs where the date jumps. Again, this ONLY happens after updating Parallels Tools.
........................
mysql-1 | 2025-09-30T12:58:52.537562Z 0 [Note] /usr/sbin/mysqld: ready for connections.
mysql-1 | Version: '5.7.33' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)
mysql-1 | 2120-11-21T23:58:02.189483Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 3002399822931ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
mysql-1 | 2120-11-21T23:58:02.829685Z 3938 [Warning] Current time has got past year 2038. Validating current time with 5 iterations before initiating the normal server shutdown process.
mysql-1 | 2120-11-21T23:58:02.829867Z 3938 [Warning] Iteration 1: Current time obtained from system is greater than 2038

 

Has there been a solution posted in the newer updates (such as the one posted in Dec. 15th)?

 

I just updated again (on accident) for the latest update. Updating the Parallel tools still kills MSQL. Long term looking to drop Parallels for linux as the Rosetta 2 going away announcement means docker may die anyway.