#Using buildctl, not able to check grpc connection test on dagger engine >=0.9.4

1 messages · Page 1 of 1 (latest)

pulsar yarrow
#

hello everyone

I am trying to do health check on engine startup(puppet),also I have grpc setting set using .toml file set to 8080
this is the command i used to check whether buildkit inside the container is running, this stop working when upgraded to engine >=0.9.4

docker exec -it dagger-engine buildctl --addr tcp://localhost:8080 debug workers -v

Error:
Error: invalid address tcp://localhost:8080 (expected unix://, got tcp://)

this usually worked in earlier version of dagger engine up until 0.9.3

Can anyone help?

naive spindle
#

Hm, that way of checking to see whether dagger is running in the container has never been explicitly supported, and we deliberately broke it when making some changes

#

I think this is part of a larger issue - there's not a good way to check the health of the dagger engine at the moment.

pulsar yarrow
#

Was there any reason to break this? also could you please recommend, may be a workaround to check anything close to see if dagger actually running

naive spindle