Hello, I have some news about this topic.
Like @deherman-MSFT said, I was using the same limits and reservations. So I changed that to use only reservations but it changed anything.
After that I tried to use another imag with the same configuration (reservations) and the deployment was working! So I was thinking that my problem is my container image that was too large (more than 1Go). So I reduced my golang image using practises explained in this blog : golang-small-docker-image
Now my containers seems to be created, I don't have the timeout error on docker compose up
. But unfortunatly the containers on azure still "Waiting", see image below.
I don't have any logs. Do you have an idea of the reason or how to debug ?
See my docker-compose.yaml below :
version: "3"
services:
node1:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-1.yaml
networks:
local:
ipv4_address: 172.28.1.101
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
node2:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-2.yaml
networks:
local:
ipv4_address: 172.28.1.102
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
node3:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-3.yaml
networks:
local:
ipv4_address: 172.28.1.103
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
node4:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-4.yaml
networks:
local:
ipv4_address: 172.28.1.104
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
node5:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-5.yaml
networks:
local:
ipv4_address: 172.28.1.105
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
node6:
build:
context: server
image: ***.azurecr.io/node-server
command: ./server -config config/neighbour-6.yaml
networks:
local:
ipv4_address: 172.28.1.106
deploy:
resources:
reservations:
cpus: '0.25'
memory: 0.1gb
client:
build:
context: client
image: ***.azurecr.io/node-client
stdin_open: true # docker run -i
tty: true # docker run -t
networks:
local:
ipv4_address: 172.28.1.50
# debug:
# image: busybox
# stdin_open: true # docker run -i
# tty: true # docker run -t
# networks:
# local:
# ipv4_address: 172.28.1.51
networks:
local:
driver: bridge
ipam:
config:
- subnet: 172.28.1.0/24
gateway: 172.28.1.1