#Generated clients GraphQL validation with external runner host error

1 messages · Page 1 of 1 (latest)

tulip mortar
#

Also, (don’t know how relevant this is) when I run dagger functions it returns no functions found - doesn’t seem to be seeing my testModule functions.

winter cave
#

Hey there 👋 I should be able to help, just a few clarifying questions

  • does this work with a local engine? or its just failing with a remote engine?
  • when you say external dagger host, how is that configured?
  • no functions for dagger functions is expected here since testModule is a dependency and wouldn't show up here
tulip mortar
#

Thanks!

  • it works when I don’t specify a value for the external dagger runner host env var.
  • I have dagger runner host and my go app docker containers defined in docker-compose with all the volumes set, privileged:true etc. Running locally

Dagger host is just the dagger host image with a pinned version, set via mounting a unix socket, configured with unix:///run/dagger/engine.sock

connection to the engine works fine, it’s just running code from the generated client that causes the error

tulip mortar
#

I wonder if it’s the way I’m building my go app binary and the fact that the modules aren’t being included

winter cave
#

I think the client will expect the dagger.json to still be there, so that's something to check. It definitely sounds like a peculiar setup so I'd be curious to hear about your use case and what you're trying to do 😅

tulip mortar
#

Just trying to run dagger functions from a go app!

winter cave
#

Nice! For CI tasks or something else? Generated clients are definitely a supported path it's not the primary way people execute dagger functions

tulip mortar
#

Yeah for CI tasks. I was using a multi stage docker file for building the go binary- I guess the paths were getting messed up

#

I think that’s the issue at least!