Brianara3

I'm having an issue starting this docker. Brand new install never run before and the mysql server won't start. I get the following errors in the mysql error.log. I have verified permissions in the container and the mysql data directories are full r/w to the mysql user and group. I have tried running the container with privileged option and get same result. I have also tried completely removing the container and appdata directories and reinstalling with no change.

Well, here we are almost a month later and I am still having the same issue with 6.10.x not working with domain-joined SMB. I have even updated 6.10.3 hoping that would improve things but it hasn't. I have tried configuring the items that @harpesichord suggested and that worked for *some* of the user accounts, but not others. I still get the same result of user shows up in wbinfo -u but get error with wbinfo -i <user>. The wbinfo -i <user> works fine for any users that are able to access shares and everything, but not for the others. I'm pulling my hair out with this one.....

Well, so much for that plan... About 24 hours later all of my clients have started losing connection to the shares. It was never an issue before upgrading to 6.10.2, but even downgrading back to 6.9.2 hasn't fully resolved the issue. I can also rule out it being a Windows specific issue, as both my Windows and Linux (via CIFS/autofs) clients lose connection with a permission denied error (or error 13 in the case of CIFS/Linux). Other users seem to be having a similar issue with 6.10 here: And I am seeing the same behavior as this one ("wbinfo -i <user>" can't find domain and "wbinfo -u" lists the usernames I am trying), but I don't think they are on 6.10: When I run the "wbinfo -i <user>" I get this response, but pinging the AD domain and FQDN of the domain controller works fine and resolves to the right IP (only 1 DC). ----- failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user <username> ----- Restarting the samba service doesn't seem to matter. Leaving the domain still appears to be broken in my 6.9.2. Rebooting the entire Unraid server seems to resolve it, but I assume it will come back again after some time. However, this takes forever since I have to stop all my VMs, docker containers, the array, reboot, and reload everything. Not to mention it seems like samba and/or docker doesn't always seem to start correctly on the first reboot... but that's another issue. I am able to get the clients back to access the shares if I create a matching username/password on Unraid locally, so it has something up with the AD authentication in Unraid.

I'm having the same issue after upgrading to 6.10.2. Initially I thought it may be a permission issue and running the "new permissions" tool seemed to resolve it, but after about a week I am getting the same error when trying to access SMB shares. I tried to leave/join the domain to see if that resolves it as well, but when I click on the leave button it thinks for a minute then nothing happens. The page reloaded but status is still "joined" and I still see the computer object in AD. Reverting back to 6.9.2 gave me access back to my shares.