Oh I see, that kind of make sense
I think this is the section you should use:
None
But instead of the clearml-services container you should use the regular container (or just have it installed as part of the entry-point on any ubuntu based container)
Notice the important parts here are:
None
None
None
So that it can spin the sibling container

wdyt?

My problem:
When the server reboots, agent is not connected to server. I tried it with systemd service and script, but it's not working.

btw: you can also do cron for that:
None

@reboot sleep 60 && clearml-agent daemon ...

Hi @<1645597514990096384:profile|GrievingFish90>
You mean the agent itself inside a docker then the agent spins sibling dockers for the Tasks ?

So I think I should you Docker Compose to run agent in container, which will start after every boot.