I am seeing in bold and yellow font:
Could not generate persistent MAC: No data available
Discussion
@a19cf39a, it looks like the error message "Could not generate persistent MAC: No data available" is related to the network interface configuration. Have you tried checking the network settings for the container?
Also, regarding the error message "0_TMPFILE is not supported on /TMP (disabling future attempts)", it seems to be related to the MySQL configuration. You may want to check the MySQL configuration file and make sure that the tmpdir setting is pointing to a valid directory.
Where is the MySQL configuration file?
The MySQL configuration file is usually located at /etc/mysql/my.cnf. You can also check the output of the following command to see the location of the configuration file:
```
sudo mysql --help | grep -A 1 "Default options"
```
This will show you the location of the configuration file and other default options.
MySQL command not found
@a19cf39a, it sounds like you may not have MySQL installed on your system. Have you installed it yet? If not, you can install it by running the following command:
```
sudo apt-get install mysql-server
```
Once it's installed, you can find the configuration file at `/etc/mysql/mysql.conf.d/mysqld.cnf`.
How can I check the network settings for the container?
You can check the network settings for a container by running the following command:
```
docker inspect
```
This will display the network settings for the container, including the IP address and the ports that are exposed. You can replace `
I see
"LinkLocalIPv6Address": " "
Is that the issue?
@a19cf39a: It's possible that the lack of a LinkLocalIPv6Address could be causing the issue. Have you tried setting a static IP address for the container and seeing if that resolves the issue? You can do this by adding the `--ip` flag followed by the desired IP address when running the `docker run` command. For example:
```
docker run --ip 172.18.0.2 myimage
```
You can replace `myimage` with the name of your MySQL image.
What does it mean when journalctl -xe shows that something has entered the 'dead' state?
When you see the message "entered the 'dead' state" in the output of `journalctl -xe`, it means that the service or unit has stopped running and will not be restarted automatically. This can happen for a variety of reasons, such as a configuration error, a crash, or a manual stop command. In order to diagnose the issue, you will need to look for error messages or other clues in the logs.