yeti icon indicating copy to clipboard operation
yeti copied to clipboard

Published 20 hours ago • verified publisher icon yeti-platform

Docker errors in scheduler

Open jekil opened this issue 6 years ago • 5 comments

Scheduler and workers are not working in docker, due to a issue in systemd. Actually this is prevented by how process are spawned in docker.

jekil avatar Jul 12 '19 11:07 jekil

Interesting. Maybe we should decouple the "installation" steps from Docker then and just have a special docker container for workers and scheduler. WDYT?

tomchop avatar Jul 12 '19 11:07 tomchop

Same problem here. There's some workarround?

naxonez avatar Jul 18 '19 07:07 naxonez

There is no workaround, the architecture of how the initial process is spawned must be changed to allow systemctl to work (now it is spawned as first process and it is now allowed by systemctl)

jekil avatar Jul 19 '19 10:07 jekil

I think it's worth spending some time to create another docker image where only the workers are started. It doesn't make sense to use startup daemons in docker images (my mistake) :D

tomchop avatar Jul 19 '19 10:07 tomchop

@jekil Can you tell me which image you're using to run Yeti in docker? We don't seem to reference systemd in them.

tomchop avatar Jul 29 '19 20:07 tomchop