Closed pfrancks closed 12 months ago
If I manually switch to the nightly branch with git checkout nightly, everything works.
same here. running generate_config.sh
isn't enough, I had to manually switch to the nightly branch. I think it's best to update the blogpost.
I am trying to deploy and test on Oracle Cloud (Ampere instance). When I clone and install from the main branch (Nightly) half of containers restart every like 20-30 seconds rendering the whole system unusable.
When I try cloning from the ARM64 branch with
git clone https://github.com/mailcow/mailcow-dockerized -b /feat/arm64-cow
I get error
Cloning into 'mailcow-dockerized'...
fatal: Remote branch /feat/arm64-cow not found in upstream origin
Is this temporary? Anyone knows what ARM processors are used in Hertzner?
Thanks
same here. running
generate_config.sh
isn't enough, I had to manually switch to the nightly branch. I think it's best to update the blogpost.
@I0tzi Can you tell me how to change the branch manually? Thanks
same here. running
generate_config.sh
isn't enough, I had to manually switch to the nightly branch. I think it's best to update the blogpost.@I0tzi Can you tell me how to change the branch manually? Thanks
git clone -b nightly https://github.com/mailcow/mailcow-dockerized
same here. running
generate_config.sh
isn't enough, I had to manually switch to the nightly branch. I think it's best to update the blogpost.@I0tzi Can you tell me how to change the branch manually? Thanks
git clone -b nightly https://github.com/mailcow/mailcow-dockerized
@l0tzi Hm, why may I be getting this error message? Thanks in advance
Cloning into 'mailcow-dockerized'...
fatal: Remote branch remotes/origin/nightly not found in upstream origin
use
git checkout nightly
inside /opt/mailcow-dockerized and than update the setup with ./update.sh
use
git checkout nightly
inside /opt/mailcow-dockerized and than update the setup with ./update.sh
This worked to set up the container, while trying to set it up like mentioned here: https://mailcow.email/posts/2023/arm64-open-beta/ didn't work (most container were restarting)
Hi, I installed Mailcow today on a Hetzner ARM VM according to the instructions. Some Docker containers use AMD64 architecture instead of ARM64. Is this a known problem?
sogo-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Are you sure you are using the nightly branch? The tag used in nightly for the sogo image have arm64 support: https://hub.docker.com/layers/mailcow/sogo/nightly-1.119/images/sha256-19d0e1c8b7fbac87c7e6a272acf2b1ad3285d071c5abbf8fcf9aa76a0b81d7b6?context=explore
Or am I missing something here? If yes, we can repush it
Hi, thank you for the quick feedback. Yes, I am using the nightly branch. Most containers are for ARM64 but not this one.
โ Network mailcowdockerized_mailcow-network Created 0.2s โ Container mailcowdockerized-redis-mailcow-1 Started 0.0s โ Container mailcowdockerized-sogo-mailcow-1 Started 0.1s โ Container mailcowdockerized-memcached-mailcow-1 Started 0.1s โ Container mailcowdockerized-solr-mailcow-1 Started 0.0s โ Container mailcowdockerized-olefy-mailcow-1 Started 0.1s โ Container mailcowdockerized-dockerapi-mailcow-1 Started 0.1s โ Container mailcowdockerized-unbound-mailcow-1 Started 0.1s โ Container mailcowdockerized-watchdog-mailcow-1 Started 0.1s โ Container mailcowdockerized-php-fpm-mailcow-1 Started 0.0s โ Container mailcowdockerized-clamd-mailcow-1 Started 0.0s โ Container mailcowdockerized-mysql-mailcow-1 Started 0.0s ! sogo-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s โ Container mailcowdockerized-nginx-mailcow-1 Started 0.0s โ Container mailcowdockerized-dovecot-mailcow-1 Started 0.1s โ Container mailcowdockerized-postfix-mailcow-1 Started 0.0s โ Container mailcowdockerized-acme-mailcow-1 Started 0.1s โ Container mailcowdockerized-rspamd-mailcow-1 Started 0.0s โ Container mailcowdockerized-ofelia-mailcow-1 Started 0.0s โ Container mailcowdockerized-netfilter-mailcow-1 Started 0.0s
I am also on the nightly build. For me those images cant be started:
! watchdog-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested ! php-fpm-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested ! postfix-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested ! acme-mailcow The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
When I pulled the nightly 3 weeks ago, all worked! https://github.com/mailcow/mailcow-dockerized/issues/5384#issuecomment-1725401414
Works now with the latest commit 45717ccdfa8995d5eeea4bc8794cb023e4401c4c The images are now pulled correctly and every container starts up.
Thanks @DerLinkman :)
Yes i've updated it as it would collide with the current staging images.
Still no ETA! So please don't get to excited.
Contribution guidelines
I've found a bug and checked that ...
Description
Steps to reproduce:
Which branch are you using?
master
Operating System:
Debian 12
Server/VM specifications:
8 GB, 4 cores, Hetzner CAX21
Is Apparmor, SELinux or similar active?
yes
Virtualization technology:
Hetzner cloud
Docker version:
24.0.5
docker-compose version or docker compose version:
v2.20.2
mailcow version:
2023-08
Reverse proxy:
none
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: