#No such host (v0.8.0+)

1 messages · Page 1 of 1 (latest)

distant heron
#

Hello lovely Dagger folks 👋

Lots of times using the bound services feature I run into the problem of no such host causing my builds to fail.
I thought I had pinned things down to this occurring more often when the bound service needed resolving before I started my foreground container. Adding a Sync before doing a WithExec(nil) and binding it appeared to have a positive effect.

That said, upgrading to the 0.8.x minor version and this has all started to fail on me. Locally, everything works nicely, however, our builds in CI all fail because of the no such host error (I think this is occurring in the healthcheck in Dagger, as opposed to surfacing in my attempts to dial in the foreground container).

Here is an example, all the failed jobs have the same problem in them, they're all dagger pipelines:
https://github.com/flipt-io/flipt/actions/runs/5889767518/job/15973555000?pr=2009

Here is the block of code that starts most of these pipelines:
https://github.com/flipt-io/flipt/blob/f9f139a50a73563de130adcc8560e5a521a149ac/build/testing/integration.go#L320-L341

Just checking in to see if you have any insights. I wouldn't be surprised if I was doing something silly in our setup. This is blocking us from moving onto the latest versions.

eager nova
#

@glass crater any insight?

glass crater
#

@distant heron do you have a health-check configured on the service? It looks like those logs appear before the service logs do (from a quick pre-coffee skim)

upper dawn
glass crater
#

yeah what marcos said 🙂

distant heron
#

Ahhh interesting, let me give that a go. I will report back!

#

I am not doing that, I am fairly sure.

upper dawn
#

@glass crater something else that's a bit strange to me is that they seem to be calling sync before adding that contaner as a service dependency. I'm wondering why sync just doesn't block the test execution since IIUC the flipt entrypoint should be a long-running process

distant heron
#

I think I do the sync before the WithExec(nil) 👆 So there is no starting a long running process up to that point.

upper dawn
distant heron
#

You might be right though and that could be part of the equation 😂
I am moving from ExitCode to Sync a lot in this PR (to bring it up to 0.8.x) and that didn't seem to be a problem for 0.6.4 and ExitCode.

upper dawn
#

well.. doesn't seem to be the case I see that both the tests and flipt are started concurrently

#

regardless.. seems like WithExposedPort should fix it

distant heron
#

Its looking like it has! Thank you all 🙇‍♂️
Down to just one test which appears to be failing this new healthcheck. Instead of all my tests going red like they were before.

Legends 🙏

upper dawn
#

🚀happy to help George!

#

just confirmed WithExec(nil) is still required, so that was it