Ad Widget

Collapse

Problem with docker-compose containers not starting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • grumpazoid
    Junior Member
    • May 2021
    • 2

    #1

    Problem with docker-compose containers not starting

    Hi.
    I am new to Zabbix.

    I am trying do deploy with docker-compose using the following: docker-compose -f ./docker-compose_v3_alpine_mysql_latest.yaml up -d

    However not all containers are pulled / run e.g. no zabbix agent. My output is not that as shown in the docs.
    OS is latest Debian - I have tried on 2 different installs and the problem is the same.

    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    WARNING: The following deploy sub-keys are not supported and have been ignored: resources.reservations.cpus
    Creating network "zabbix-docker_zbx_net_backend" with driver "bridge"
    Creating network "zabbix-docker_zbx_net_frontend" with driver "bridge"
    Creating network "zabbix-docker_default" with the default driver
    Creating zabbix-docker_db_data_mysql_1 ... done
    Creating zabbix-docker_mysql-server_1 ... done
    Creating zabbix-docker_zabbix-server_1 ... done
    Creating zabbix-docker_zabbix-web-nginx-mysql_1 ... done

    What am I doing wrong?

  • grumpazoid
    Junior Member
    • May 2021
    • 2

    #2
    I have also now tried with Ubuntu server and get the same result?

    Comment

    • bordwalk2000
      Junior Member
      • Jul 2022
      • 1

      #3
      I also have the same results. Not all the containers specified in the docker-compose file are created and I don't understand why.




      user@zabbix:/opt/zabbix-docker$ sudo docker-compose ps -a
      Name Command State Ports
      ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
      zabbix-docker_db_data_mysql_1 sh Exit 0
      zabbix-docker_mysql-server_1 docker-entrypoint.sh mysql ... Up
      zabbix-docker_zabbix-server_1 /sbin/tini -- /usr/bin/doc ... Up 0.0.0.0:10051->10051/tcp,:::10051->10051/tcp
      zabbix-docker_zabbix-web-nginx-mysql_1 docker-entrypoint.sh Up (healthy) 0.0.0.0:80->8080/tcp,:::80->8080/tcp, 0.0.0.0:443->8443/tcp,:::443->8443/tcp


      Comment

      • Nosfy
        Junior Member
        • Aug 2022
        • 2

        #4
        Hello,

        I also face the same issue:
        All containers start, then after few seconds db-container ( does not matter is I try postgre or mysql ) exits with code 0 and logs for web say:
        Code:
        **** MySQL server is not available. Waiting 5 seconds...
        Restart of container or setting it in restart-always does not change a thing.

        I do suspect something is wrong with db connection but have no idea how to figure our what exactly,
        Any help will be appreciated,

        Thank you.

        Comment

        • Nosfy
          Junior Member
          • Aug 2022
          • 2

          #5
          Originally posted by Nosfy
          Hello,

          I also face the same issue:
          All containers start, then after few seconds db-container ( does not matter is I try postgre or mysql ) exits with code 0 and logs for web say:
          Code:
          **** MySQL server is not available. Waiting 5 seconds...
          Restart of container or setting it in restart-always does not change a thing.

          I do suspect something is wrong with db connection but have no idea how to figure our what exactly,
          Any help will be appreciated,

          Thank you.
          So this was gixed by changing network to
          Code:
          internal: false
          And now I have issue with DB:
          Code:
          Database error:
          ----
          Unable to select configuration
          Have to say that other colleagues of mine have no issues with pretty much the same config:
          - Hyper-V
          - Ubuntu Server 22
          - Latest Docker
          - Latest Docker-compose

          Comment

          Working...