milkmaker
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Closed SoulofAkuma closed 2 years ago
milkmaker
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
SoulofAkuma
commented
2 years ago Am I missing the obvious here or is it quite the contrary? Does anyone have an idea what could cause all these errors?
milkmaker
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
eddiewebb
commented
1 year ago uhhh, anyone want to respond instead of marking it stale?
dodedodo
commented
1 year ago Given the failed writes/missing file I'd say take a look at permissions and check if you're not out of diskspace. Maybe you're running docker as non-root?
Try asking around on the mailcow telegram, there are a lot of smart people active there.
eddiewebb
commented
1 year ago Thanks @dodedodo - it was actually Ubunutu snap's installation of docker/Lxc, tore that out and things were fine.
XVII
commented
1 year ago @eddiewebb did you have any more insight into your solution? I saw lxd was installed via snap and removed it (not used), but still getting dns resolution issues inside by containers...
sudo snap remove lxd@ShadowXVII it was a prior box i dont have that command history,but I currently have 0 snap packages and know docker was installed direct per their docs.
root@localhost:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
apt-get update
apt-get install ca-certificates curl gnupg lsb-release
mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
apt-get update
apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin
Prior to placing the issue, please check following: (fill out each checkbox with an
Xonce done)Summary
After the old "undockerized" version of mailcow, which was set up on the server by someone else, stopped working, I decided to set up the dockerized mailcow version three days ago and since then I've tried to fix the issues I've had with the dockerized one, but no luck. I've first tried to set it up with apache as a proxy but after apache gave me repeated proxy errors I've tried it without. Still, trying to curl the HTTP port still got me a
curl: (56) Recv failure: Connection reset by peer. If I use my browser, I get anERR_CONNECTION_RESETorERR_CONNECTION_CLOSED. Telnet also doesn't work (telnet: Unable to connect to remote host: Connection refused). The logs repeatedly show MySQL, Redis, and DNS errors for various containers. I've attached the output ofnestat -tulpnat the end of the issue, to show that docker is listening on these ports, but that's all that shows any sign of success on my machine network-wise. I'll happily provide any required information.Logs
Logs from postfix and dovecot related to DNS (these occur periodically in the logs)
Logs from sogo and ofelia related to Redis (watchdog and acme repeatedly print
Waiting for... redis) (these also repeatedly occur periodically in the logs)Logs from sogo related to MySQL error (these also repeatedly occur periodically in the logs):
Reproduction
I was not able to reproduce the issue on another machine. I've tried it on another local development VM and it worked there. However, on the machine it isn't working on, I've been able to reproduce it every time. As to what I've done to fix it, here's a list:
systemctl --type=service | grep running)System information
docker version)docker-compose version)Output from
iptables -L -vnOutput from
iptables -L -vn -t natOutput from
ip6tables -L -vnOutput from
ip6tables -L -vn -t natI've made no network modifications, but there are DNS problems.
Output of
systemctl --type=service | grep runningOutput of
netstat -tulpn