Well, I have been trying to import a MariaDB SQL dump file for about three months now and I think it's time to just call it and start over. You see I had problems with MariaDB one day after a power failure and it would either work or not. Later that day I redeployed it and it pulled the latest image and that's when it just died. Mind you I'm still new to Kubernetes and set up my cluster with k3s due to not having all that many resources when it comes to donated Computers. That means I will need to start fresh with my Friendca node since that is what MariaDB was being used for. It sucks to start over but sometimes there is no way around it.
Now let's move on to what I have dealt with when it comes to asking for any kind of help when relating to MariaDB or more specifically. Let's go with the fact I was first told to run a set of commands and it would just fix the issues I was having. The funny thing is that was not true. It did nothing to address the problems I was facing and I was not the only one facing them either. So I did some more digging and noted something odd. What I noted was the fact there was a permissions problem somewhere that was not there before. That means that either k3s changed them due to how the image was put together or the image failed to change the permissions to what it needed to be. So I look into how to export and import a database. My problem of not having many resources has made importing an almost 60-gigabyte file harder than it needs to be.
Now a good thing about all of this is that I have learned what to do and what not to do when it comes to k3s and Docker images. Anyway don't have too much fun or at least try not to.