* Improve tty error logging when buildkit vertex is unknown
Creates a generic "system" group in the tty output which captures
buildkit events that report a non-dagger vertex name. This happens
currently when using core.#Dockerfile actions since Dagger delegates the
LLB generation to buildkit through it's frontend and we don't get
meaningful events that we can correlate from Dagger's side
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
Add a method that will retrieve the version, the running state and the network host existence of the buildkitd container.
If the version is outdated or there is no host network, we delete the container and install a proper one.
If the container is correctly configured but is not active, we start it, which saves some time.
Signed-off-by: Lucas Perreau <lucas.perreau@ext.adeo.com>
