Warning after docker-compose: Server not accessible

[Xinnerpeace]

Summary

Warning after docker-compose: Server not accessible

Steps to reproduce

Followed install guide from Open Source is Awesome. https://wiki.opensourceisawesome.com/books/freesccout-support-software-that-starts-with-email/page/freescout-support-starting-with-email

Relevant logs and/or screenshots

app log:

2023-12-12 18:05:15 2023-12-12.18:05:15 [NOTICE] ** [monitoring] Container configured for monitoring with 'zabbix modern'
2023-12-12 18:05:17 2023-12-12.18:05:17 [NOTICE] ** [scheduling] Container configured for scheduled tasks with 'cron'
2023-12-12 18:05:17 2023-12-12.18:05:17 [NOTICE] ** [messaging] Container configured to route mail via SMTP to 'postfix-relay'
2023-12-12 18:05:19 2023-12-12.18:05:19 [NOTICE] ** [php-fpm] Creating sample index.php
2023-12-12 18:05:25 2023-12-12.18:05:25 [WARN] ** [freescout] Potential New Installation / Standalone Installation Detected - Copying Freescout Sourcecode
2023-12-12 18:05:33 2023-12-12.18:05:33 [WARN] ** [freescout] Detected /data directory. Persistently saving settings/sessions/cache/uploads/modules
2023-12-12 18:05:39 2023-12-12.18:05:39 [WARN] ** [freescout] MySQL/MariaDB Server 'freescout-db' is not accessible, retrying.. (5 seconds so far)

db log:

2023-12-12 18:05:10 2023-12-12.10:05:10 [NOTICE] ** [scheduling] Disabling Scheduling
2023-12-12 18:05:10 sed: /etc/logrotate.d/mariadb: No such file or directory
2023-12-12 18:05:10 2023-12-12.10:05:10 [WARN] ** [mariadb] MariaDB directory already present, skipping database creation
2023-12-12 18:05:10 2023-12-12.10:05:10 [WARN] ** [mariadb] Installed version: 10.11.6, but image version: 10.6.7
2023-12-12 18:05:10 2023-12-12.10:05:10 [WARN] ** [mariadb] Upgrading databases to 10.6.7 version
2023-12-12 18:05:16 2023-12-12.10:05:16 [WARN] ** [mariadb] MySQL/MariaDB Server '127.0.0.1' is not accessible, retrying.. (5 seconds so far)

Environment

• Image version / tag: latest
• Host OS: Windows Server 2019 Standard

Docker-compose.yml:

services:
  freescout-app:
    image: tiredofit/freescout
    container_name: freescout-app
    ports:
    - 8252:80
    links:
    - freescout-db
    volumes:
    ### If you want to perform customizations to the source and have access to it, then uncomment this line - This includes modules
    #- ./data:/www/html
    ### Or, if you just want to use Stock Freescout and hold onto persistent files like cache and session use this, one or the other.
    - ./data:/data
    ### If you want to just keep the original source and add additional modules uncomment this line
    - ./modules:/www/html/Modules
    - ./logs/:/www/logs
    environment:
    - CONTAINER_NAME=freescout-app    
    - DB_HOST=freescout-db
    - DB_NAME=freescout
    - DB_USER=freescout
    - DB_PASS=freescout
    - SITE_URL=http://192.168.0.197:8252
    - ADMIN_EMAIL=example@example.com
    - ADMIN_PASS=freescout
    - ENABLE_SSL_PROXY=FALSE
    - DISPLAY_ERRORS=FALSE
    restart: always

  freescout-db:
    image: tiredofit/mariadb
    container_name: freescout-db
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - ROOT_PASS=password
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=freescout
      - CONTAINER_NAME=freescout-db
    restart: always

  freescout-db-backup:
    container_name: freescout-db-backup
    image: tiredofit/db-backup
    links:
     - freescout-db
    volumes:
      - ./dbbackup:/backup
    environment:
      - CONTAINER_NAME=freescout-db-backup
      - DB_HOST=freescout-db
      - DB_TYPE=mariadb
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=freescout
      - DB01_BACKUP_INTERVAL=1440
      - DB01_BACKUP_BEGIN=0000
      - DB_CLEANUP_TIME=8640
      - COMPRESSION=BZ
      - MD5=TRUE
    restart: always

[tarasis]

Same issue using latest docker image, and the example config

freescout-db is constantly printing out this to the console

freescout-db         | exec /init: exec format error
freescout-db exited with code 1

The other two run fine freescout-app & freescout-db-backup

---

Google suggests it is likely an issue with binary type

Exec format error usually means that the binary is for a different cpu or different libc. Like arm vs x86 or glibc vs musl. ETA: It can also happen if the bit size is wrong. For example if you have 32-bit x86 binaries running on a 64-bit amd64 system but don't have the 32-bit libraries installed.

Which is feasible, the host I am trying to run the docker container on is Arm. I don't think any of the servers I have available to me are x86_64/amd64.

---

No, I'm wrong, I do have one, and yes using the same docker-compose.yml on that server works. freescout-db comes up as expected.