Thank you very much 🙂 I don't think our Data team ever use this container so I will stop it for now and comment it from the compose file

• What are the credentials that are referred to in the logs? Where do I get these?
• How do I ensure this container is run automatically if it keeps restarting using the docker-compose file?
• If I run sudo docker run -it allegroai/clearml-agent-services:latest manually, do I need to put this in a crontab? My knowledge of running docker containers is a bit limited.
• Does this service need to run if I already have a clearml-agent running on a separate instance?

Hi @<1687643893996195840:profile|RoundCat60> ,

What are the credentials that are referred to in the logs? Where do I get these?

These are part of the server's docker-compose configuration. See here: None

How do I ensure this container is run automatically if it keeps restarting using the docker-compose file

I'm not sure I understand - docker-compose will constantly try to run the container. Right now, it's failing, so it just keeps trying.

If I run 

sudo docker run -it allegroai/clearml-agent-services:latest

 manually, do I need to put this in a crontab? My knowledge of running docker containers is a bit limited.

There's no need to use crontab as this is handled by docker-compose

Does this service need to run if I already have a clearml-agent running on a separate instance?

This is a complementary server service - it's not required and nothing else depends on it - it's just a convenience for executing cpu-only maintenance tasks (services) on the server's machine - you can absolutely disable it if you don't need it (or even just ignore the errors 😄 )