ikoyhn

I also was getting that error that was nearly crashing my server. The issue is the database command yarn database:setup, what I had to do to fix this was clear my postgresDB and run the command yarn database:migrate instead. Seems the issue is the default data that gets inserted using the setup version of the command. In reality I wouldn't think this error should cause CPU overload, maybe the authors of the project could lower the amount of logs written?

Don't forget to right click on the container -> console and run ` yarn database:setup ` after the rest of the setup. Thanks for the guide looking forward to checking this out!

New Bedrock update, can no longer join server as it is out of date, any ETA on a docker update? Thanks!