Sites fail to boot or create on Fedora 39

What issue or error are you experiencing?

  • mysql service is spewing out errors, and can not start


  • The error does not exist when using MySql 5.7.
  • I have reinstalled Local
  • I have tried it on existing sites that worked fine in Fedora 38
  • I have tried adding a fresh site, it still does not work
  • I have run a fresh, clean install of Fedora 39 in a VM, and it fails there as well. It’s a bit different though, but still related to the MySQL service
  • I have tested it with a VM and Fedora 38, and there Local works fine.

If anyone knows a solution or quick fix, it would be greatly appreciated.


What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

  • Install Fedora 39 on your machine, or in a VM
  • Install the latest Local release
  • Just add a new site in Local and start it, or start an existing site, and the error will pop-up.

System Details

  • Local Version:
  • 8.1.0
  • Operating System (OS) and OS version:
  • Fedora 39
  • I am using docker for other development need, but during testing no containers were running

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-lightning-verbose.log (55.5 KB)


Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

Cross sharing this thread with one of our Local Devs that might provide some helpful information as well. If you have related questions or concerns you can also share over there as well:

Thanks Nick for sharing some information. I will look into that.

(Interesting addition that came accross: the default Docker image of WordPress does not work well on Fedora 39 either in most docker-compose setups I have seen, the container is running, but it will result in err_connection_reset. From Locals perspective, this will return a 502 as nginx can not connect to the container)

1 Like