Hi Prefect Team - We are able to start a docker container on our linux box to act as an agent. The agent is started and the work-queue can be started as well. Should we start this docker container from systemd to restart it in case it crashes?

hi @Chris Gunderson - this might be helpful. yeah systemd is typically what we recommend if you're running a worker (or agent) on a VM if you're just getting set up, I'd recommend a worker, as they are more configurable and designed to be next gen agents

@Nate Thanks Nate. I was using this example. I wanted to use a docker container, so we can point to two different workspaces on the same Linux box.

i think you could have 2 different systemd services, with different api_urls, which run docker workers. so they'd be regular systemd processes, but the flow runs they submit (for their respective workspace) would be containers

@Nate I tried that, but got the failures above.

i dont often see people run the worker process itself as a container like that, is there a reason you're doing that? because you have

prefect worker start -t docker

, each flow run will be submitted as a new container to the docker engine available to the worker process, so I'm actually not sure how that would work if the worker process itself is running as a container usually, running the worker as a systemd process that submits flow runs as containers to the VMs docker engine is what I see people doing