• Community Support
  • USEnglish
  • Auto start Mailcow at server rebbot

How can I get mailcow to restart whenever the server is rebooted.? It seems I have to manually do the “docker compose up -d” command. there MUST be some way of autostarting mailcow at boot. Anyone done this ?

  • deeprip likes this.
  • Sorry, I see nothing in the documentation referring to “autostart”.
    The content referring to Starting it has the following: No reference to autostart. What am i missing?

    Start mailcow¶

    Pull the images and run the compose file. The parameter -d will start mailcow: dockerized detached:
    docker compose (Plugin)
    docker-compose (Standalone)

    docker compose pull
    docker compose up -d

    Done!

    You can now access https://${MAILCOW_HOSTNAME} with the default credentials admin + password moohoo.

    Info

    If you are not using mailcow behind a reverse proxy, you should redirect all HTTP requests to HTTPS.

    The database will be initialized right after a connection to MySQL can be established.

    Your data will persist in multiple Docker volumes, that are not deleted when you recreate or delete containers. Run docker volume ls to see a list of all volumes. You can safely run docker compose down without removing persistent data.
    Last update: 2022-12-16 19:22:13

    OK, ignore my question. I have it now . Thanks

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!

Sorry, I see nothing in the documentation referring to “autostart”.
The content referring to Starting it has the following: No reference to autostart. What am i missing?

Start mailcow¶

Pull the images and run the compose file. The parameter -d will start mailcow: dockerized detached:
docker compose (Plugin)
docker-compose (Standalone)

docker compose pull
docker compose up -d

Done!

You can now access https://${MAILCOW_HOSTNAME} with the default credentials admin + password moohoo.

Info

If you are not using mailcow behind a reverse proxy, you should redirect all HTTP requests to HTTPS.

The database will be initialized right after a connection to MySQL can be established.

Your data will persist in multiple Docker volumes, that are not deleted when you recreate or delete containers. Run docker volume ls to see a list of all volumes. You can safely run docker compose down without removing persistent data.
Last update: 2022-12-16 19:22:13

OK, ignore my question. I have it now . Thanks

6 months later

For anyone who comes across this in the future, just enable the docker service to start at bootup and the mailcow containers will start automatically unless you made manual changes to the docker-compose.yaml file.
On Linux, the command is
sudo systemctl enable docker
to start docker at boot.

No one is typing