#Where do containers run?
lusty drum
I didn't really know about buildkit, but from this: https://docs.docker.com/build/buildkit/ it seems like just the image builder engine, and not a container runtime/orchestrator
Where do containers run?
sharp jungle
I did recall this being discussed briefly and found it: #docker message
lusty drum
He says there that > at the system level (linux cgroups, namespaces etc) you will see dagger-managed and docker-managed containers side by side
So guessing there should be a way to see these containers with docker ps or some other way, but it’s not clear to me how. Anyway, maybe the real question I should ask is whether dagger supports multiple agents/workers and in general parallelism
sharp jungle
You'll see the resource consumption of other containers you're running with Docker and the containers Dagger is running for you in cgtop. They're not Docker containers so docker ps isn't going to show them.
For the latter question, the Dagger engine supports multiple concurrent requests (I don't actually know how many, we've never had enough requests to try and figure that out, or reason enough to care yet), but without Dagger Cloud you'll likely lose caching. If you describe the general pipeline structures I'm sure one of the Dagger team can be more specific
lusty drum
wdym lose caching? can you elaborate? 🙂
sharp jungle
If you have one Dagger engine instance and all clients are sending requests to that instance they'll all benefit from caching. If you put X Dagger engines behind an autoscaling group and your request hits a difference instance it won't have the cache from the previous instance... unless you use a cloud cache like Dagger Cloud