OK so I followed docs.mailcow.email Icon the guide for migrating a Mailcow instance

docs.mailcow.email Icon docs.mailcow.email
Migration - mailcow: dockerized documentation
None
docs.mailcow.email
, but the thing is I couldn’t rsync to the root user, so I rsynced to another user and in my infinite wisdom just chowned all of them to root:root, including /opt/mailcow-dockerized and /var/lib/docker/volumes/*

It was stuck on “Preparing”, and it told me to check the PHP container, which said Waiting for SQL, so I checked mailcowdockerized-mysql-mailcow-1, which is saying:

2024-09-29  9:26:48 0 [ERROR] mysqld: Can't create/write to file '/run/mysqld/mysqld.pid' (Errcode: 13 "Permission denied")

2024-09-29  9:26:48 0 [ERROR] Can't start server: can't create PID file: Permission denied

Also, I checked /var/lib/docker/volumes/mailcowdockerized_mysql-vol-1/_data/ and it all seemed to belong to 999:systemd-journal.

I couldn’t exec into the MySQL container, but I tried making an Alpine container, mounting the volume, and chowning everything to mysql:mysql and that seemed to work, but it didn’t last.

Please save me from my own idiocy

–Quokka.

    quokka couldn’t rsync to the root user

    Why not? I suggest you start all over again and this time rsync it the way it’s supposed to be

      Have something to say?

      Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

      Wait I fixed it by doing chown -R 999:systemd-journal /var/lib/docker/volumes/mailcowdockerized_mysql-socket-vol-1/_data/ 👍👍👍

      Also how do you close issues here?

      Also how do you close issues here?

      Hmm, but that’s only this directory, others still could have the wrong permissions… good luck with that…

      No one is typing