Docker compose project name - 500 Internal Server Error

[aronmal]

Contribution guidelines

• [X] I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• [X] ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
• [X] ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• [X] ... I have understood that answers are voluntary and community-driven, and not commercial support.
• [X] ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

I normally started mailcow with docker-compose up -d. I updated last week to Compose v2. Worked fine. I installed additionally a plugin for my Unraid OS, which stats with -p flag for a project name like docker-compose -p mailcow_dockerized up -d. This project name argument results into an "500 Internal Server Error" by SOGo and "Error 502 Bad gateway" for the admin panel. Found that out by the network name in the console output which seems to relate to the project name ("mailcowdockerzied" as default?):

root@Tower:/mnt/user/appdata/compose/mailcow-dockerized# docker compose up -d
[+] Running 20/20
 ⠿ Network mailcowdockerized_mailcow-network  Crea...                                             0.3s
 ⠿ Container mailcow-memcached                Started                                             8.0s
 ⠿ Container mailcow-dockerapi                Started                                            10.7s
 ⠿ Container mailcow-sogo                     Started           
...

root@Tower:/mnt/user/appdata/compose/mailcow-dockerized# cat up.sh 
docker compose -p mailcow_dockerized up -d
root@Tower:/mnt/user/appdata/compose/mailcow-dockerized# ./up.sh
[+] Running 20/20
 ⠿ Network mailcow_dockerized_mailcow-network  Cr...                                              0.3s
 ⠿ Container mailcow-redis                     Started                                           11.7s
 ⠿ Container mailcow-memcached                 Started                                            8.7s
 ⠿ Container mailcow-dockerapi                 Started     
...

Should that be expected? And the default "mailcowdockerized" being required or is this not supposed to happen? I found three entries in this repository, but I am not sure how this conflicts.

Logs

Can not access logs when in the error state. I was very confused at the beginning, but I at least  found the source of the error.

Steps to reproduce

1. Start the mailcow stack with the -p flag and a project name.

System information

Question	Answer
My operating system	Unraid
Is Apparmor, SELinux or similar active?	IDK
Virtualization technology (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported	bare matel
Server/VM specifications (Memory, CPU Cores)	Intel® Xeon® Gold 6130 - 64GB RAM
Docker version (docker version)	20.10.14
docker-compose version (docker-compose version)	v2.5.0
mailcow version (git describe --tags `git rev-list --tags --max-count=1` )	2022-06b
Reverse proxy (custom solution)	SWAG

Output of git diff origin/master, any other changes to the code? If so, please post them:

root@Tower:/mnt/user/appdata/compose/mailcow-dockerized# git diff origin/master
diff --git a/data/conf/postfix/main.cf b/data/conf/postfix/main.cf
index a445b60c..ddecac7e 100644
--- a/data/conf/postfix/main.cf
+++ b/data/conf/postfix/main.cf
@@ -198,3 +198,6 @@ parent_domain_matches_subdomains = debug_peer_list,fast_flush_domains,mynetworks
 
 # DO NOT EDIT ANYTHING BELOW #
 # User overrides #
+
+myhostname = *SENSORED_HOSTNAME*
+
diff --git a/docker-compose.yml b/docker-compose.yml
index a563df91..1e9656eb 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -615,7 +615,7 @@ networks:
     driver: bridge
     driver_opts:
       com.docker.network.bridge.name: br-mailcow
-    enable_ipv6: true
+    enable_ipv6: false
     ipam:
       driver: default
       config:

All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn:

YOUR OUTPUT GOES HERE

ip6tables -L -vn:

YOUR OUTPUT GOES HERE

iptables -L -vn -t nat:

YOUR OUTPUT GOES HERE

ip6tables -L -vn -t nat:

YOUR OUTPUT GOES HERE

DNS problems? Please run docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and post the output:

YOUR OUTPUT GOES HERE