Mailcow-dockerized: Installing from dev

Created on 31 Jul 2017  Â·  7Comments  Â·  Source: mailcow/mailcow-dockerized

Hey guys, I'm trying to install from DEV but I'm getting this silly message:

WARNING: The DBROOT variable is not set. Defaulting to a blank string.
WARNING: The DBNAME variable is not set. Defaulting to a blank string.
WARNING: The DBUSER variable is not set. Defaulting to a blank string.
WARNING: The DBPASS variable is not set. Defaulting to a blank string.
WARNING: The MAILCOW_HOSTNAME variable is not set. Defaulting to a blank string.
WARNING: The TZ variable is not set. Defaulting to a blank string.
WARNING: The ADDITIONAL_SAN variable is not set. Defaulting to a blank string.
and cannot continue.

The installation already generates mailcow.conf and everything seems to be fine inside the file, perhaps it doesn't work.

any tip? thanks.

All 7 comments

Run docker-compose from within the mailcow folder. Or specify the path in command line.

Am 31.07.2017 um 14:48 schrieb alyzrazor notifications@github.com:

Hey guys, I'm trying to install from DEV but I'm getting this silly message:

WARNING: The DBROOT variable is not set. Defaulting to a blank string.
WARNING: The DBNAME variable is not set. Defaulting to a blank string.
WARNING: The DBUSER variable is not set. Defaulting to a blank string.
WARNING: The DBPASS variable is not set. Defaulting to a blank string.
WARNING: The MAILCOW_HOSTNAME variable is not set. Defaulting to a blank string.
WARNING: The TZ variable is not set. Defaulting to a blank string.
WARNING: The ADDITIONAL_SAN variable is not set. Defaulting to a blank string.
and cannot continue.

The installation already generates mailcow.conf and everything seems to be fine inside the file, perhaps it doesn't work.

any tip? thanks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I did that, perhaps there is something more. I downloaded the file manually, because I don't know the dev's link for cloning like: git clone https://github.com/mailcow/mailcow-dockerized && cd mailcow-dockerized

I tried git clone https://github.com/mailcow/mailcow-dockerized-dev && cd mailcow-dockerized and nothing happens. =(

ln -s mailcow.conf .env should be enough then. :-)

Dev may not be stable.

Am 31.07.2017 um 15:48 schrieb alyzrazor notifications@github.com:

I did that, perhaps there is something more. I downloaded the file manually, because I don't know the dev's link for cloning like: git clone https://github.com/mailcow/mailcow-dockerized && cd mailcow-dockerized

I tried git clone https://github.com/mailcow/mailcow-dockerized-dev && cd mailcow-dockerized and nothing happens. =(

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I didn't quite get what you say @andryyy :P sorry
I tried renaming mailcow.conf to mailcow.env but no luck =(

this is what I get at the very end and everything freezes up:
:/home/ubuntu/mailcow-dockerized-dev# docker-compose up -d

WARNING: The DBROOT variable is not set. Defaulting to a blank string.
WARNING: The DBNAME variable is not set. Defaulting to a blank string.
WARNING: The DBUSER variable is not set. Defaulting to a blank string.
WARNING: The DBPASS variable is not set. Defaulting to a blank string.
WARNING: The MAILCOW_HOSTNAME variable is not set. Defaulting to a blank string.
WARNING: The TZ variable is not set. Defaulting to a blank string.
WARNING: The ADDITIONAL_SAN variable is not set. Defaulting to a blank string.
Creating network "mailcowdockerizeddev_mailcow-network" with driver "bridge"
Creating volume "mailcowdockerizeddev_crypt-vol-1" with default driver
Creating volume "mailcowdockerizeddev_redis-vol-1" with default driver
Creating volume "mailcowdockerizeddev_vmail-vol-1" with default driver
Creating volume "mailcowdockerizeddev_postfix-vol-1" with default driver
Creating volume "mailcowdockerizeddev_rspamd-vol-1" with default driver
Creating volume "mailcowdockerizeddev_mysql-vol-1" with default driver
Creating volume "mailcowdockerizeddev_dkim-vol-1" with default driver
Creating mailcowdockerizeddev_mysql-mailcow_1 ...
Creating mailcowdockerizeddev_clamd-mailcow_1 ...
Creating mailcowdockerizeddev_ipv6nat_1 ...
Creating mailcowdockerizeddev_clamd-mailcow_1
Creating mailcowdockerizeddev_mysql-mailcow_1
Creating mailcowdockerizeddev_clamd-mailcow_1 ... done

Naa, you need to create a link, not rename that file. :-) ln -s mailcow.conf .env

Thanks @andryyy Finally I managed to install Dev version today.
There was another error while installing: RED_COLOR Dovecot 1.6 doesn't exist or something like that, then it took way longer than usual to install though.

Yes, I have not pushed this image yet. It builds it then.

Am 01.08.2017 um 18:21 schrieb alyzrazor notifications@github.com:

Thanks @andryyy Finally I managed to install Dev version today.
There was another error while installing: RED_COLOR Dovecot 1.6 doesn't exist or something like that, then it took way longer than usual to install though.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

phipag picture phipag  Â·  3Comments

GalacticLion7 picture GalacticLion7  Â·  3Comments

schoebelh picture schoebelh  Â·  3Comments

bonanza123 picture bonanza123  Â·  3Comments

Braintelligence picture Braintelligence  Â·  3Comments