viscid dagger
I'm looking to an issue with Docker authentication (You can see it for reference: https://discord.com/channels/707636530424053791/1313155675572011049). One of the difficulty I'm encountering is the fact that the dagger-engine image doesn't contains the docker binary. So I asked to ChatGPT what he thinks about it (why not?) and this is its answer:
The dagger-engine Docker image is designed to serve as the core of Dagger, a modern CI/CD platform. As of now, the image does not include the Docker binary itself. Instead, the Dagger engine communicates with Docker by using a Docker-in-Docker (DinD) container or a host's Docker socket for executing containerized workloads.
Key Points:
Docker Binary: The dagger-engine image doesn't bundle the docker CLI binary because its primary focus is on serving as a backend engine for Dagger workflows, not running Docker commands directly.
I always have thought that the dagger-engine has the responsability to open the buildkit socket where the client can communicate with it and also have the responsability to handle the containers.
- Am I wrong or is ChatGPT hallucinating there?
- Where does Dagger handle the docker authentication to registries? Is on the engine or the client side?
narrow kestrel