Gremmi

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by Gremmi

  1. Thank you guys .. I switched the IP4-assignment now to "NONE" and was able to set up the network manually in docker-settings. Now it´s also possible to type in a gateway.

     

    Earlier I changed for testing the NGINX docker image to port 1480 and 1443 and it came up on the wrong ip (10.10.10.120). Now after the changes it uses 10.10.14.120 (perfect) but it fails on both ports:

    Quote

    tcp 10.10.14.120:1480: bind: cannot assign requested address

     

    I can use every port I want to but it fails always. Something I forgot?

  2. Hello again,

     

    since I´m trying to install mailcow on unraid (without additional VM) I´m facing the next problem and hopefully you can give me a hind how to solve it ;)

     

    What I´m trying:

     

    * I have two NICs installed (see picture)

    * One NIC should be used for the "internal" network. Unraid should be available only on this NIC

    * Second NIC should be used for mailcow and is connected to the VLAN of my internet DMZ. The second NIC should only be available for mailcow running on docker

     

    I chaned my NIC settings but in the moment I´m changing eth1 and saving the settings unraid is not available via network (ssh, web-gui). I found a video (thank you Spaceinvader) where I found the information "unraid is grabbing all network interfaces". He excluded the interface and used it for the VM he created.

     

    Now my questions :):

     

    * Do I have to do it the same way?

    * Since I don´t have a VM where can I configure eth1 since unraid is not handling it anymore?

     

     

    Thank you for your help .. and sorry for the bad picture ;)

     

     

    unraid-mailcow.jpg

    unraid-nics.jpg

  3. ... and I´m back :)

     

    What I have done

     

    mkdir /opt/mailcow-dockerized
    mkdir /mnt/user/appdata/mailcow/mailcow-dockerized
    
    mount --bind /opt/mailcow-dockerized /mnt/user/appdata/mailcow/mailcow-dockerized
    
    cd /opt
    git clone https://github.com/mailcow/mailcow-dockerized
    cd mailcow-dockerized

     

    I started the containers (one failed but my fault .. wrong config). I restarted unraid .... aaaaaaaaand: Everything is gone :o

     

    "/opt/mailcow-dockerized" => OK because it has to be mounted manually (later via go script) but what I really don´t understand: Why is the folder "/mnt/user/appdata/mailcow/mailcow-dockerized" empty?!?

     

  4. Hey,

     

    I´m just evaluating unraid (I think I will buy a license :)). Currently I have a fully overpowered NAS with several virtual machines. My plan is to use a low power hardware in the future and ebay will take care of my old NAS.

    Now I just tried to install Mailcow (my mail actual mail solution) with unraid but it was not that easy I expected:

    docker-compose: Since the CA don´t have compose on board anymore I decided to use docker-compose as docker image with an alias (

    Seems to do it´s job good :). Check.

    The installation manual of mailcow ask to do clone the git repo to /opt/mailcow-dockerized

    Since I learned unraid is unpacking every time in RAM and the only persistent volumes are /boot, /mnt/diskX and /mnt/cache “opt” would probably the wrong place to clone the repo to. I would need an additional data directory where the configuration and data is stored.

     

    This is my point I´m a little bit stuck because I´m not sure which solution is the “unraid-way” to solve the problem:

    ·         Create the directories via ssh in /mnt/diskX ? Or is this per default a bad idea?

    ·         Create the directories with the gui?

    Maybe I´m doing it totally wrong?

    Some ppl are suggesting to use a VM to install Mailcow but I have a bad feeling to have a system with docker and all I need and create a VM to only host a mailsys into.

     

    Thank you for your help in advance. Maybe someone is using mailcow already (I think @GuildDarts is using it this way too :)

     

    Cheers

    Gremmi