Docker Swarm issues on one node

[rimelek (Ákos Takács)]

@jeans72

I have defined ‘Depend On’ on Stacks for Services/Containers. Anything else could be done to make cleaner startup?

Interesting that it comes up twice in a day. @bluepuma77 already answered it, and the other was about compose, but that doesn’t matter so I leave it here. So you have to implement the waiting and reconnecting or just let the container restart unti it an finally connect.

How to handle server reboot when using docker-compose?

Docker Compose is a kind of client for Docker. Features that Docker doesn’t support are used for developement and in some cases to make sure the first started container can initialize data which will be mounted by another container as well. So when you first start the container, the order of the containers are more important. I never used the depends_on feature with healthchecks as the applications should handle when a dependency is not available. If the app fails because it can’t access an endp…

Regarding the first question

@jeans72

HW dependent (stateless?).

That is not really what stateless is.The hardware is not the state of the application, handled data is.
Everything is hardware dependent by the way. The question is just how much, but you will not run an amd64 application on an arm cpu without emulation.

@jeans72

it crashes with exist code 132.

I could return that exit code any time in a shell script, so that depends on what application you run, but it looks like it is usually a CPU compatibility issue which you already know as you tried different CPU settings for the Proxmox VMs. It is still something we solve without knowing the application, and even then there is no guarantee we will have an idea. Maybe you can contact the developers of the application or a community that supports it and ask what CPU requirements it has.

On the other hand, the fact that the container is not scheduled automatically on that node, could mean that even Docker can tell you that wouldn’t work. So I would check the difference between the architecture of the VMs and any other hardware difference.