-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mailcow in RHEL8 podman/buildah/skopeo #2614
Comments
It looks like podman can interpret Dockerfiles, so this should be relatively easy. There is even a docker-compose replacement: https://github.com/muayyad-alsadi/podman-compose. However we cannot support multiple different containerization frameworks simultaneously without a lot of manual work (see the tickets about Kubernetes support), so Mailcow is going to stay Docker-only. |
can you revisit this? podman-compose can use a lot of what docker-compose provides, so it's nearly compatible. If you look at what docker-compose.yml features you use and what is supported you may be able to provide "support" for podman-compose just by doing a few small changes. If you want to reopen this, I'd be glad to have a look. I just don't know if I can be done within the next 3-4 months. But I think if you'd label this as "wontfix" instead of closing it there'd be a better understanding of what feature requests are not feasible at the moment. As far as I see it you're not totally against supporting podman, right? |
The Dockerfiles and docker-compose would indeed be compatible. However, Mailcow interfaces with the Docker API for some of its functionality, which would have to be rewritten. Also, I am unaware of what kind of IPv6 support podman has -- in Docker, we require a special piece of software to configure NAT and that only works on Docker. Very recent versions of Docker have native IPv6 NAT support, but we have not tested that yet and from what I hear it's still quite beta. If someone adapts our dockerapi.py to Podman in a minimally-invasive way and finds a simple solution to the IPv6 problem, we could certainly consider providing official (but best-effort only) support. If it requires any major maintenance effort, I don't see it happening because Docker is still way more common than its alternatives and most people are running Mailcow on dedicated Docker instances. |
Podman 3.0.0 seems to get a proper compatibility API for Docker. Maybe it will work without rewriting the interface? Are there integration tests which one could run against such a setup?
Podman has some serious bugs which have to be resolved before it has 100% functional IPv6 functionality. The most important seems to be containers/netavark#340 as it's about Podman being compatible with the IPv6 functionality of Docker.
That sounds lovely! Can you re-open this Issue then so it won't be forgotten? |
I'd like to add to this discussion by saying that podman offers some security features that docker does not (e.g. podman does not need to run with sudo) and it allows integration with cockpit web gui. |
also podman 3.x is available on bullseye which was released yesterday... will test on debian if this support ever happens :) |
another happy tester for debian/podman here! 😄 |
Hello, I tried it as well, but I failed: I did the following steps: curl -L https://github.com/docker/compose/releases/download/$(curl -Ls https://www.servercow.de/docker-compose/latest.php)/docker-compose-$(uname -s)-$(uname -m) > /usr/local/sbin/docker-compose
chmod +x /usr/local/sbin/docker-compose Installed podman-docker: dnf install podman-docker -y systemctl enable podman.socket --now Generated mailcow config file. --- docker-compose.yml.inc 2021-09-03 14:59:49.104506087 +0200
+++ docker-compose.yml 2021-09-23 11:09:56.318691496 +0200
@@ -615,7 +615,7 @@
driver: default
config:
- subnet: ${IPV4_NETWORK:-172.22.1}.0/24
- - subnet: ${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}
+ #- subnet: ${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}
volumes:
vmail-vol-1: Error: [root@abydos mailcow-dockerized]# docker-compose up -d
Creating network "mailcowdockerized_mailcow-network" with driver "bridge"
Creating volume "mailcowdockerized_vmail-vol-1" with default driver
Creating volume "mailcowdockerized_vmail-index-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-socket-vol-1" with default driver
Creating volume "mailcowdockerized_redis-vol-1" with default driver
Creating volume "mailcowdockerized_rspamd-vol-1" with default driver
Creating volume "mailcowdockerized_solr-vol-1" with default driver
Creating volume "mailcowdockerized_postfix-vol-1" with default driver
Creating volume "mailcowdockerized_crypt-vol-1" with default driver
Creating volume "mailcowdockerized_sogo-web-vol-1" with default driver
Creating volume "mailcowdockerized_sogo-userdata-backup-vol-1" with default driver
Creating mailcowdockerized_clamd-mailcow_1 ... done
Creating mailcowdockerized_unbound-mailcow_1 ... done
Creating mailcowdockerized_dockerapi-mailcow_1 ... done
Creating mailcowdockerized_watchdog-mailcow_1 ... done
Creating mailcowdockerized_memcached-mailcow_1 ... done
Creating mailcowdockerized_redis-mailcow_1 ... done
Creating mailcowdockerized_sogo-mailcow_1 ... done
Creating mailcowdockerized_solr-mailcow_1 ... done
Creating mailcowdockerized_olefy-mailcow_1 ... done
Creating mailcowdockerized_mysql-mailcow_1 ... done
Creating mailcowdockerized_php-fpm-mailcow_1 ... done
Creating mailcowdockerized_dovecot-mailcow_1 ... error
Creating mailcowdockerized_postfix-mailcow_1 ...
Creating mailcowdockerized_nginx-mailcow_1 ...
ERROR: for mailcowdockerized_dovecot-mailcow_1 Cannot start service dovecot-mailcow: error configuring network namespace for container d8cf73369bfda68ee181fc1ecbdcd51036215f796aab39Creating mailcowdockerized_postfix-mailcow_1 ... error
r range 0: requested IP address 172.22.1.250 is not available in range set 172.22.1.1-172.22.1.254
ERROR: for mailcowdockerized_postfix-mailcow_1 Cannot start service postfix-mailcow: error configuring network namespace for container 5e27fbfd330a5f31eaabe680ed66db8d8fec33cc705520d74f9786dc721886fc: error adding pod mailcowdockerized_postfix-mailcow_1_mailcowdockerized_postfix-mailcow_1 to CNI network "mailcowdockerized_mailcow-network": failed to allocate foCreating mailcowdockerized_nginx-mailcow_1 ... done
Creating mailcowdockerized_acme-mailcow_1 ... done
ERROR: for dovecot-mailcow Cannot start service dovecot-mailcow: error configuring network namespace for container d8cf73369bfda68ee181fc1ecbdcd51036215f796aab39c8a9fc5c5f9f33350d: error adding pod mailcowdockerized_dovecot-mailcow_1_mailcowdockerized_dovecot-mailcow_1 to CNI network "mailcowdockerized_mailcow-network": failed to allocate for range 0: requested IP address 172.22.1.250 is not available in range set 172.22.1.1-172.22.1.254
ERROR: for postfix-mailcow Cannot start service postfix-mailcow: error configuring network namespace for container 5e27fbfd330a5f31eaabe680ed66db8d8fec33cc705520d74f9786dc721886fc: error adding pod mailcowdockerized_postfix-mailcow_1_mailcowdockerized_postfix-mailcow_1 to CNI network "mailcowdockerized_mailcow-network": failed to allocate for range 0: requested IP address 172.22.1.253 is not available in range set 172.22.1.1-172.22.1.254
ERROR: Encountered errors while bringing up the project.
[root@abydos mailcow-dockerized]# What is the difference? Or where are my faults? Cheers, |
@Mordecaine If you attach the compose file, I think you could usefully file the above as a ticket against https://github.com/containers/podman - would be worth also asking about the IPv6 question too...? |
@ramcq Thats a good point. I'll created an issue at the podman team: But it is funny, that @libesz does not have these kind of problems. |
👍
I think he meant he was happy to test, not that he had it working already. :) |
Exactly 😄 . I am planning to migrate a legacy email server soon to mailcow and I plan to do it with podman if it is possible. |
I have tested against The remaining services that fail are |
that's pretty close to working conditions because:
|
Latest update for the status. I have able to start the whole stack successfully with some modification. dnf install -y git podman pip
pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz
loginctl enable-linger $(whoami)
systemctl --user start podman.socket
cd /opt
git clone https://github.com/mailcow/mailcow-dockerized
cd mailcow-dockerized
// replace the file below before the command
./generate_config.sh
// startup
podman-compose -p mailcowdockerized up -d
// shutdown
podman-compose -p mailcowdockerized down @unixfox Some question. podman psSuccessful printout CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eef56dc923a4 docker.io/mailcow/unbound:1.16 /usr/sbin/unbound 8 minutes ago Up 8 minutes ago mailcowdockerized_unbound-mailcow_1
7e183a8e14f4 docker.io/library/redis:7-alpine redis-server 7 minutes ago Up 7 minutes ago 127.0.0.1:7654->6379/tcp mailcowdockerized_redis-mailcow_1
8420f09e2b4c docker.io/mailcow/sogo:1.112 /bin/sh -c exec /... 7 minutes ago Up 7 minutes ago mailcowdockerized_sogo-mailcow_1
bb172e844db1 docker.io/library/memcached:alpine memcached 7 minutes ago Up 7 minutes ago mailcowdockerized_memcached-mailcow_1
7f49b91b30d0 docker.io/mailcow/watchdog:1.96 /bin/sh -c /watch... 7 minutes ago Up 7 minutes ago mailcowdockerized_watchdog-mailcow_1
9b7f56b5a76a docker.io/mailcow/dockerapi:1.42 python3 -u /app/d... 7 minutes ago Up 7 minutes ago mailcowdockerized_dockerapi-mailcow_1
c128e6f39ba1 docker.io/mailcow/solr:1.8.1 /solr.sh 7 minutes ago Up 7 minutes ago 127.0.0.1:18983->8983/tcp mailcowdockerized_solr-mailcow_1
800250ed20d1 docker.io/mailcow/olefy:1.10 python3 -u /app/o... 7 minutes ago Up 7 minutes ago mailcowdockerized_olefy-mailcow_1
9465a2a78b04 docker.io/library/mariadb:10.5 mysqld 7 minutes ago Up 7 minutes ago 127.0.0.1:13306->3306/tcp mailcowdockerized_mysql-mailcow_1
efb10f1ffaf8 docker.io/mailcow/clamd:1.54 /sbin/tini -g -- ... 7 minutes ago Up 7 minutes ago (healthy) mailcowdockerized_clamd-mailcow_1
e67dd080c8cc docker.io/mailcow/phpfpm:1.80 php-fpm -d date.t... 7 minutes ago Up 7 minutes ago mailcowdockerized_php-fpm-mailcow_1
06769be5b54f docker.io/mailcow/dovecot:1.20 /bin/sh -c exec /... 7 minutes ago Up 7 minutes ago 127.0.0.1:19991->12345/tcp, 0.0.0.0:110->110/tcp, 0.0.0.0:143->143/tcp, 0.0.0.0:993->993/tcp, 0.0.0.0:995->995/tcp, 0.0.0.0:4190->4190/tcp mailcowdockerized_dovecot-mailcow_1
a795ddca9a8c docker.io/mailcow/postfix:1.68 /bin/sh -c exec /... 7 minutes ago Up 7 minutes ago 0.0.0.0:25->25/tcp, 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp mailcowdockerized_postfix-mailcow_1
1426d3e6d761 docker.io/mailcow/rspamd:1.91 /usr/bin/rspamd -... 7 minutes ago Up 7 minutes ago mailcowdockerized_rspamd-mailcow_131ddcc3230c5 docker.io/library/nginx:mainline-alpine /bin/sh -c envsub... 7 minutes ago Up 7 minutes ago 127.0.0.1:80->80/tcp, 127.0.0.1:443->443/tcp mailcowdockerized_nginx-mailcow_1
40da1c7f16b0 docker.io/mailcow/acme:1.82 /sbin/tini -g -- ... 7 minutes ago Up 7 minutes ago mailcowdockerized_acme-mailcow_1
aeadf6ca3462 docker.io/mcuadros/ofelia:latest daemon --docker 7 minutes ago Up 7 minutes ago mailcowdockerized_ofelia-mailcow_171475d7067e8 docker.io/mailcow/netfilter:1.49 python3 -u /serve... 7 minutes ago Up Less than a second ago mailcowdockerized_netfilter-mailcow_1 generate_config.sh
#!/usr/bin/env bash
set -o pipefail
if [[ "$(uname -r)" =~ ^4\.15\.0-60 ]]; then
echo "DO NOT RUN mailcow ON THIS UBUNTU KERNEL!";
echo "Please update to 5.x or use another distribution."
exit 1
fi
if [[ "$(uname -r)" =~ ^4\.4\. ]]; then
if grep -q Ubuntu <<< $(uname -a); then
echo "DO NOT RUN mailcow ON THIS UBUNTU KERNEL!";
echo "Please update to linux-generic-hwe-16.04 by running \"apt-get install --install-recommends linux-generic-hwe-16.04\""
exit 1
fi
fi
if grep --help 2>&1 | head -n 1 | grep -q -i "busybox"; then echo "BusyBox grep detected, please install gnu grep, \"apk add --no-cache --upgrade grep\""; exit 1; fi
# This will also cover sort
if cp --help 2>&1 | head -n 1 | grep -q -i "busybox"; then echo "BusyBox cp detected, please install coreutils, \"apk add --no-cache --upgrade coreutils\""; exit 1; fi
if sed --help 2>&1 | head -n 1 | grep -q -i "busybox"; then echo "BusyBox sed detected, please install gnu sed, \"apk add --no-cache --upgrade sed\""; exit 1; fi
#for bin in openssl curl docker git awk sha1sum; do
# if [[ -z $(which ${bin}) ]]; then echo "Cannot find ${bin}, exiting..."; exit 1; fi
#done
for bin in openssl curl podman git awk sha1sum; do
if [[ -z $(which ${bin}) ]]; then echo "Cannot find ${bin}, exiting..."; exit 1; fi
done
#if docker compose > /dev/null 2>&1; then
# if docker compose version --short | grep "^2." > /dev/null 2>&1; then
# COMPOSE_VERSION=native
# echo -e "\e[31mFound Docker Compose Plugin (native).\e[0m"
# echo -e "\e[31mSetting the DOCKER_COMPOSE_VERSION Variable to native\e[0m"
# sleep 2
# echo -e "\e[33mNotice: You´ll have to update this Compose Version via your Package Manager manually!\e[0m"
# else
# echo -e "\e[31mCannot find Docker Compose with a Version Higher than 2.X.X.\e[0m"
# echo -e "\e[31mPlease update/install it manually regarding to this doc site: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m/i_u_m_install/\e[0m"
# exit 1
# fi
#elif docker-compose > /dev/null 2>&1; then
# if ! [[ $(alias docker-compose 2> /dev/null) ]] ; then
# if docker-compose version --short | grep "^2." > /dev/null 2>&1; then
# COMPOSE_VERSION=standalone
# echo -e "\e[31mFound Docker Compose Standalone.\e[0m"
# echo -e "\e[31mSetting the DOCKER_COMPOSE_VERSION Variable to standalone\e[0m"
# sleep 2
# echo -e "\e[33mNotice: For an automatic update of docker-compose please use the update_compose.sh scripts located at the helper-scripts folder.\e[0m"
# else
# echo -e "\e[31mCannot find Docker Compose with a Version Higher than 2.X.X.\e[0m"
# echo -e "\e[31mPlease update/install manually regarding to this doc site: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m/i_u_m_install/\e[0m"
# exit 1
# fi
# fi
#
#else
# echo -e "\e[31mCannot find Docker Compose.\e[0m"
# echo -e "\e[31mPlease install it regarding to this doc site: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m/i_u_m_install/\e[0m"
# exit 1
#fi
COMPOSE_VERSION=native
if [ -f mailcow.conf ]; then
read -r -p "A config file exists and will be overwritten, are you sure you want to continue? [y/N] " response
case $response in
[yY][eE][sS]|[yY])
mv mailcow.conf mailcow.conf_backup
chmod 600 mailcow.conf_backup
;;
*)
exit 1
;;
esac
fi
echo "Press enter to confirm the detected value '[value]' where applicable or enter a custom value."
while [ -z "${MAILCOW_HOSTNAME}" ]; do
read -p "Mail server hostname (FQDN) - this is not your mail domain, but your mail servers hostname: " -e MAILCOW_HOSTNAME
DOTS=${MAILCOW_HOSTNAME//[^.]};
if [ ${#DOTS} -lt 2 ] && [ ! -z ${MAILCOW_HOSTNAME} ]; then
echo "${MAILCOW_HOSTNAME} is not a FQDN"
MAILCOW_HOSTNAME=
fi
done
if [ -a /etc/timezone ]; then
DETECTED_TZ=$(cat /etc/timezone)
elif [ -a /etc/localtime ]; then
DETECTED_TZ=$(readlink /etc/localtime|sed -n 's|^.*zoneinfo/||p')
fi
while [ -z "${MAILCOW_TZ}" ]; do
if [ -z "${DETECTED_TZ}" ]; then
read -p "Timezone: " -e MAILCOW_TZ
else
read -p "Timezone [${DETECTED_TZ}]: " -e MAILCOW_TZ
[ -z "${MAILCOW_TZ}" ] && MAILCOW_TZ=${DETECTED_TZ}
fi
done
MEM_TOTAL=$(awk '/MemTotal/ {print $2}' /proc/meminfo)
if [ ${MEM_TOTAL} -le "2621440" ]; then
echo "Installed memory is <= 2.5 GiB. It is recommended to disable ClamAV to prevent out-of-memory situations."
echo "ClamAV can be re-enabled by setting SKIP_CLAMD=n in mailcow.conf."
read -r -p "Do you want to disable ClamAV now? [Y/n] " response
case $response in
[nN][oO]|[nN])
SKIP_CLAMD=n
;;
*)
SKIP_CLAMD=y
;;
esac
else
SKIP_CLAMD=n
fi
if [ ${MEM_TOTAL} -le "2097152" ]; then
echo "Disabling Solr on low-memory system."
SKIP_SOLR=y
elif [ ${MEM_TOTAL} -le "3670016" ]; then
echo "Installed memory is <= 3.5 GiB. It is recommended to disable Solr to prevent out-of-memory situations."
echo "Solr is a prone to run OOM and should be monitored. The default Solr heap size is 1024 MiB and should be set in mailcow.conf according to your expected load."
echo "Solr can be re-enabled by setting SKIP_SOLR=n in mailcow.conf but will refuse to start with less than 2 GB total memory."
read -r -p "Do you want to disable Solr now? [Y/n] " response
case $response in
[nN][oO]|[nN])
SKIP_SOLR=n
;;
*)
SKIP_SOLR=y
;;
esac
else
SKIP_SOLR=n
fi
echo "Which branch of mailcow do you want to use?"
echo ""
echo "Available Branches:"
echo "- master branch (stable updates) | default, recommended [1]"
echo "- nightly branch (unstable updates, testing) | not-production ready [2]"
sleep 1
while [ -z "${MAILCOW_BRANCH}" ]; do
read -r -p "Choose the Branch with it´s number [1/2] " branch
case $branch in
[2])
MAILCOW_BRANCH="nightly"
;;
*)
MAILCOW_BRANCH="master"
;;
esac
done
if [ ! -z "${MAILCOW_BRANCH}" ]; then
git_branch=${MAILCOW_BRANCH}
fi
git fetch --all
git checkout -f $git_branch
[ ! -f ./data/conf/rspamd/override.d/worker-controller-password.inc ] && echo '# Placeholder' > ./data/conf/rspamd/override.d/worker-controller-password.inc
cat << EOF > mailcow.conf
# ------------------------------
# mailcow web ui configuration
# ------------------------------
# example.org is _not_ a valid hostname, use a fqdn here.
# Default admin user is "admin"
# Default password is "moohoo"
MAILCOW_HOSTNAME=${MAILCOW_HOSTNAME}
# Password hash algorithm
# Only certain password hash algorithm are supported. For a fully list of supported schemes,
# see https://mailcow.github.io/mailcow-dockerized-docs/models/model-passwd/
MAILCOW_PASS_SCHEME=BLF-CRYPT
# ------------------------------
# SQL database configuration
# ------------------------------
DBNAME=mailcow
DBUSER=mailcow
# Please use long, random alphanumeric strings (A-Za-z0-9)
DBPASS=$(LC_ALL=C </dev/urandom tr -dc A-Za-z0-9 | head -c 28)
DBROOT=$(LC_ALL=C </dev/urandom tr -dc A-Za-z0-9 | head -c 28)
# ------------------------------
# HTTP/S Bindings
# ------------------------------
# You should use HTTPS, but in case of SSL offloaded reverse proxies:
# Might be important: This will also change the binding within the container.
# If you use a proxy within Docker, point it to the ports you set below.
# Do _not_ use IP:PORT in HTTP(S)_BIND or HTTP(S)_PORT
# IMPORTANT: Do not use port 8081, 9081 or 65510!
# Example: HTTP_BIND=1.2.3.4
# For IPv4 leave it as it is: HTTP_BIND= & HTTPS_PORT=
# For IPv6 see https://mailcow.github.io/mailcow-dockerized-docs/post_installation/firststeps-ip_bindings/
HTTP_PORT=80
HTTP_BIND=127.0.0.1
HTTPS_PORT=443
HTTPS_BIND=127.0.0.1
# ------------------------------
# Other bindings
# ------------------------------
# You should leave that alone
# Format: 11.22.33.44:25 or 12.34.56.78:465 etc.
SMTP_PORT=25
SMTPS_PORT=465
SUBMISSION_PORT=587
IMAP_PORT=143
IMAPS_PORT=993
POP_PORT=110
POPS_PORT=995
SIEVE_PORT=4190
DOVEADM_PORT=127.0.0.1:19991
SQL_PORT=127.0.0.1:13306
SOLR_PORT=127.0.0.1:18983
REDIS_PORT=127.0.0.1:7654
# Your timezone
# See https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for a list of timezones
# Use the row named 'TZ database name' + pay attention for 'Notes' row
TZ=${MAILCOW_TZ}
# Fixed project name
# Please use lowercase letters only
COMPOSE_PROJECT_NAME=mailcowdockerized
# Used Docker Compose version
# Switch here between native (compose plugin) and standalone
# For more informations take a look at the mailcow docs regarding the configuration options.
# Normally this should be untouched but if you decided to use either of those you can switch it manually here.
# Please be aware that at least one of those variants should be installed on your maschine or mailcow will fail.
DOCKER_COMPOSE_VERSION=${COMPOSE_VERSION}
# Set this to "allow" to enable the anyone pseudo user. Disabled by default.
# When enabled, ACL can be created, that apply to "All authenticated users"
# This should probably only be activated on mail hosts, that are used exclusivly by one organisation.
# Otherwise a user might share data with too many other users.
ACL_ANYONE=disallow
# Garbage collector cleanup
# Deleted domains and mailboxes are moved to /var/vmail/_garbage/timestamp_sanitizedstring
# How long should objects remain in the garbage until they are being deleted? (value in minutes)
# Check interval is hourly
MAILDIR_GC_TIME=7200
# Additional SAN for the certificate
#
# You can use wildcard records to create specific names for every domain you add to mailcow.
# Example: Add domains "example.com" and "example.net" to mailcow, change ADDITIONAL_SAN to a value like:
#ADDITIONAL_SAN=imap.*,smtp.*
# This will expand the certificate to "imap.example.com", "smtp.example.com", "imap.example.net", "smtp.example.net"
# plus every domain you add in the future.
#
# You can also just add static names...
#ADDITIONAL_SAN=srv1.example.net
# ...or combine wildcard and static names:
#ADDITIONAL_SAN=imap.*,srv1.example.com
#
ADDITIONAL_SAN=
# Additional server names for mailcow UI
#
# Specify alternative addresses for the mailcow UI to respond to
# This is useful when you set mail.* as ADDITIONAL_SAN and want to make sure mail.maildomain.com will always point to the mailcow UI.
# If the server name does not match a known site, Nginx decides by best-guess and may redirect users to the wrong web root.
# You can understand this as server_name directive in Nginx.
# Comma separated list without spaces! Example: ADDITIONAL_SERVER_NAMES=a.b.c,d.e.f
ADDITIONAL_SERVER_NAMES=
# Skip running ACME (acme-mailcow, Let's Encrypt certs) - y/n
SKIP_LETS_ENCRYPT=n
# Create seperate certificates for all domains - y/n
# this will allow adding more than 100 domains, but some email clients will not be able to connect with alternative hostnames
# see https://wiki.dovecot.org/SSL/SNIClientSupport
ENABLE_SSL_SNI=n
# Skip IPv4 check in ACME container - y/n
SKIP_IP_CHECK=n
# Skip HTTP verification in ACME container - y/n
SKIP_HTTP_VERIFICATION=n
# Skip ClamAV (clamd-mailcow) anti-virus (Rspamd will auto-detect a missing ClamAV container) - y/n
SKIP_CLAMD=${SKIP_CLAMD}
# Skip SOGo: Will disable SOGo integration and therefore webmail, DAV protocols and ActiveSync support (experimental, unsupported, not fully implemented) - y/n
SKIP_SOGO=n
# Skip Solr on low-memory systems or if you do not want to store a readable index of your mails in solr-vol-1.
SKIP_SOLR=${SKIP_SOLR}
# Solr heap size in MB, there is no recommendation, please see Solr docs.
# Solr is a prone to run OOM and should be monitored. Unmonitored Solr setups are not recommended.
SOLR_HEAP=1024
# Allow admins to log into SOGo as email user (without any password)
ALLOW_ADMIN_EMAIL_LOGIN=n
# Enable watchdog (watchdog-mailcow) to restart unhealthy containers
USE_WATCHDOG=y
# Send watchdog notifications by mail (sent from watchdog@MAILCOW_HOSTNAME)
# CAUTION:
# 1. You should use external recipients
# 2. Mails are sent unsigned (no DKIM)
# 3. If you use DMARC, create a separate DMARC policy ("v=DMARC1; p=none;" in _dmarc.MAILCOW_HOSTNAME)
# Multiple rcpts allowed, NO quotation marks, NO spaces
#[email protected],[email protected],[email protected]
#WATCHDOG_NOTIFY_EMAIL=
# Notify about banned IP (includes whois lookup)
WATCHDOG_NOTIFY_BAN=n
# Subject for watchdog mails. Defaults to "Watchdog ALERT" followed by the error message.
#WATCHDOG_SUBJECT=
# Checks if mailcow is an open relay. Requires a SAL. More checks will follow.
# https://www.servercow.de/mailcow?lang=en
# https://www.servercow.de/mailcow?lang=de
# No data is collected. Opt-in and anonymous.
# Will only work with unmodified mailcow setups.
WATCHDOG_EXTERNAL_CHECKS=n
# Enable watchdog verbose logging
WATCHDOG_VERBOSE=n
# Max log lines per service to keep in Redis logs
LOG_LINES=9999
# Internal IPv4 /24 subnet, format n.n.n (expands to n.n.n.0/24)
# Use private IPv4 addresses only, see https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses
IPV4_NETWORK=172.22.1
# Internal IPv6 subnet in fc00::/7
# Use private IPv6 addresses only, see https://en.wikipedia.org/wiki/Private_network#Private_IPv6_addresses
IPV6_NETWORK=fd4d:6169:6c63:6f77::/64
# Use this IPv4 for outgoing connections (SNAT)
#SNAT_TO_SOURCE=
# Use this IPv6 for outgoing connections (SNAT)
#SNAT6_TO_SOURCE=
# Create or override an API key for the web UI
# You _must_ define API_ALLOW_FROM, which is a comma separated list of IPs
# An API key defined as API_KEY has read-write access
# An API key defined as API_KEY_READ_ONLY has read-only access
# Allowed chars for API_KEY and API_KEY_READ_ONLY: a-z, A-Z, 0-9, -
# You can define API_KEY and/or API_KEY_READ_ONLY
#API_KEY=
#API_KEY_READ_ONLY=
#API_ALLOW_FROM=172.22.1.1,127.0.0.1
# mail_home is ~/Maildir
MAILDIR_SUB=Maildir
# SOGo session timeout in minutes
SOGO_EXPIRE_SESSION=480
# DOVECOT_MASTER_USER and DOVECOT_MASTER_PASS must both be provided. No special chars.
# Empty by default to auto-generate master user and password on start.
# User expands to [email protected]
# LEAVE EMPTY IF UNSURE
DOVECOT_MASTER_USER=
# LEAVE EMPTY IF UNSURE
DOVECOT_MASTER_PASS=
# Let's Encrypt registration contact information
# Optional: Leave empty for none
# This value is only used on first order!
# Setting it at a later point will require the following steps:
# https://mailcow.github.io/mailcow-dockerized-docs/troubleshooting/debug-reset_tls/
ACME_CONTACT=
# WebAuthn device manufacturer verification
# After setting WEBAUTHN_ONLY_TRUSTED_VENDORS=y only devices from trusted manufacturers are allowed
# root certificates can be placed for validation under mailcow-dockerized/data/web/inc/lib/WebAuthn/rootCertificates
WEBAUTHN_ONLY_TRUSTED_VENDORS=n
EOF
mkdir -p data/assets/ssl
chmod 600 mailcow.conf
# copy but don't overwrite existing certificate
echo "Generating snake-oil certificate..."
# Making Willich more popular
openssl req -x509 -newkey rsa:4096 -keyout data/assets/ssl-example/key.pem -out data/assets/ssl-example/cert.pem -days 365 -subj "/C=DE/ST=NRW/L=Willich/O=mailcow/OU=mailcow/CN=${MAILCOW_HOSTNAME}" -sha256 -nodes
echo "Copying snake-oil certificate..."
cp -n -d data/assets/ssl-example/*.pem data/assets/ssl/
# Set app_info.inc.php
if [ ${git_branch} == "master" ]; then
mailcow_git_version=$(git describe --tags `git rev-list --tags --max-count=1`)
elif [ ${git_branch} == "nightly" ]; then
mailcow_git_version=$(git rev-parse --short $(git rev-parse @{upstream}))
mailcow_last_git_version=""
else
mailcow_git_version=$(git rev-parse --short HEAD)
mailcow_last_git_version=""
fi
mailcow_git_commit=$(git rev-parse origin/${git_branch})
mailcow_git_commit_date=$(git log -1 --format=%ci @{upstream} )
if [ $? -eq 0 ]; then
echo '<?php' > data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_VERSION="'$mailcow_git_version'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_LAST_GIT_VERSION="";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_OWNER="mailcow";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_REPO="mailcow-dockerized";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_URL="https://github.com/mailcow/mailcow-dockerized";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_COMMIT="'$mailcow_git_commit'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_COMMIT_DATE="'$mailcow_git_commit_date'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_BRANCH="'$git_branch'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_UPDATEDAT='$(date +%s)';' >> data/web/inc/app_info.inc.php
echo '?>' >> data/web/inc/app_info.inc.php
else
echo '<?php' > data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_VERSION="'$mailcow_git_version'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_LAST_GIT_VERSION="";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_OWNER="mailcow";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_REPO="mailcow-dockerized";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_URL="https://github.com/mailcow/mailcow-dockerized";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_COMMIT="";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_GIT_COMMIT_DATE="";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_BRANCH="'$git_branch'";' >> data/web/inc/app_info.inc.php
echo ' $MAILCOW_UPDATEDAT='$(date +%s)';' >> data/web/inc/app_info.inc.php
echo '?>' >> data/web/inc/app_info.inc.php
echo -e "\e[33mCannot determine current git repository version...\e[0m"
fi
docker-compose.yml
|
Not necessary but if you don't use the unbound DNS resolver you won't be able to query the DNSBL database for combating against SPAM, but everything will still work without that. |
Sad, without I believe something can be done on |
Honestly, with podman all this custom networking stuff should just be dropped and replaced with |
It would be a big NO for me and the current setup already using
It would be glad if you can provide some configuration or setup for what you have mention. |
You can run mailcow in the mode of relying on native Docker IPv6 NAT, removing the ipv6nat container which is hopefully a better fit for podman. But I think it's worthwhile to make sure that things like mailcow can work in a podman world - the whole point of having compatibility with the docker-compose ecosystem is to let users take advantage of all of the examples which are out there, not just say they should do everything over again with Kubernetes pods etc. |
So you're already using mailcow with podman? With root or rootless?
With
Sadly no (working) configuration yet, I'm just tinkering with containerized mail servers like mailcow or mailu from time to time, but I didn't achieve
all at once yet (all of them are a must for me), so I don't run any mail server yet right now. |
Yes
Both, root and rootless are tested.
Yes, it faces a lot of difficulty. But it creates the commands that most fit The fact is that when you need to use
It would be a good chance to figure out if |
Indeed, they should just put out a new release, without
Not sure how to use that with |
I managed to get Mailcow working with Podman + systemd with minimal effort and only minor changes to the
|
Can't you instead set docker.io as a default registry: https://halukkarakaya.medium.com/how-to-configure-default-search-registries-in-podman-ea930289692? This way no need to change the docker-compose.yml for this line. |
Have you tried other Linux distributions? P:S: My Issue #5483 has been closed with remarks "no podman support". As a lot of Linux distribution have replaced docker by podman and docker does not support |
For Podman the future way will be
|
With Podman 4.6.1, netavark 1.7.0 on AlmaLinux 9.3 I frequently ran into an issue where traffic of Mailcow containers (at least Postfix) would freeze. I could not trace this problem down to a specific ip6tables chain. I suspected mailcow-netfilter and therefore disabled Mailcow's fail2ban. I hope this holds. The dirty workaround when it breaks: Compose down, flush nftables/iptables/ip6tables, |
Describe the solution you'd like
I'd like to be able to install and run mailcow in/with RHEL8's bundled docker replacement
podman buildah skopeo
or maybe some "able" person could translate/convert the docker-compose plz?
thx in advance
The text was updated successfully, but these errors were encountered: