Hello , I have created Docker containers using Docker-compose and ran them using docker stack deploy commands version: "3" services: web: # replace username/repo:tag with your name and image details image: client:latest command: "/app/startserver.sh ${hostname}" deploy: rep…

I think I caught the issue . Its with the memory . My service container takes 38% and all the 3 web takes 44.8% . So this lead to crash . Increase in my memory or maintaing it to 2 should work :slight_smile: Thanks a lot for your response .

I just checked . If the replica service for web is 2 . Then it works fine . When I increase it it kills once the containers are up . :frowning: Any idea folks about this behaviour.

can you use docker logs container_id for one of the containers that ended to see if they will provide an error?

[image] ebala90: I did . I dont see anything odd. :frowning: . As soon as the container is up did you look at the logs AFTER the container ends?

Damn :cry:, In the client I am downloading a file from artifact and then start the same . Seems all of 3 containers have stopped in the miidle of the download process . :open_mouth: i think it should be something related to timeout . As with 2 containers its able to process when I increase the time…

sorry, no idea… what is the source of the download? “a file from artifact”???

From Jfrog-artifactory . It works fine with 2 . … strange …

ok, i have never seen a problem with artifactory like this… i might try this manually (a script to download the artifacts) and run it multiple times concurrently to see if you can replicate the problem without containers and find the cause.

I am gonna try to add this now deploy: restart_policy: condition: on-failure delay: 5s max_attempts: 3 window: 120s I think the window is the key to ask the engine to wait before restarting

well, that is a workaround… but not a fix… it will come back to bite you again sometime…

Docker Services shutsdown once its up . How to avoid it

Docker Engine Compose

ebala90 (bk) December 29, 2017, 1:01pm 4

I did . I dont see anything odd. . As soon as the container is up , new containers are spinned up and old ones are removed . happening when I increase the replica to 3 fow web

Topic		Replies	Views
One of the container never comes up Docker Desktop docker	0	817	March 23, 2017
Docker Compose seems to start containers multiple times General	1	4801	April 6, 2018
The "docker compose up -d" command does not finish General	3	1642	November 18, 2023
Mage runs properly using docker run -dit, but exits using docker stack deploy -c General docker	2	2569	August 31, 2017
Docker kills all processes after 5 min and then restarts again automatically General docker , swarm	2	1159	July 30, 2024

Docker Services shutsdown once its up . How to avoid it

Related topics