Open UnMenorqui opened 3 months ago
Facing the same issue... It also avoids being able to deploy databases
Same issue here: v4.0.0-beta.319
I have the same issue too
Still facing the same issue here on v4.0.0-beta.329...
The issue of not being able to deploy seems to come from the fact that compose files, on which databases and premade templates are based upon, need heavy changes to work on swarm, which prevent them from running there. Swarm support is still experimental, as someone said on the discord:
I'd say that Docker swarm is 30% supported. Left and right there are hard breaks in code for docker swarm, so functionality is not always implemented. Give it a try I'd say
Description
After configuring a swarm cluster, and trying to add the manager and worker nodes on Coolify, the "Validate & Install" process get's stuck on "Docker minimum version", which actually I got v26 of docker. (Tried with v25 and upper versions between 24 and 26 which is the latest)
I tried setting up on Ubuntu 20, 22 and 24 LTS versions as the dependencies of the project rely on docker itself.
The process seems to work fine, it validates everyting but the "Docker minimum version" check keeps loading. I even left it for 24 hours as i couldn't find any logs on /data/coolify/logs.
On worker nodes, the error is clear "this is not a swarm manager, try docker swarm init", even if its a worker. Setting a swarm cluster with all manager nodes also not possible because of "Docker minimum version" check.
After some time, closing the right panel the server eventually appears as "validated" but it's impossible to deploy anything on it.
I tried setting coolify on a separated instance from the swarm cluster ( 1 manager, and 3 workers) and even as a service on a swarm cluster but the swarm nodes verification keeps getting stuck.
Minimal Reproduction (if possible, example repository)
Same for worker node but different error. (no swarm manager, try swarm init).
Exception or Error
Could not find any logs on /data/coolify/logs Container logs are not useul as its a server configuration issue between coolify and docker swarm.
Version
v4.0.0-beta.297