#Chainable API for working with Helm char...

1 messages · Page 1 of 1 (latest)

remote lake
#

@distant sandal I'm checking with the team on this...sorry for the frustration

distant sandal
#

Thanks! I'm out of ideas, so any help would be much appreciated.

I think the new API looks much nicer and technically it works (the problematic part is the test, because it binds an OCI registry).

bronze bear
#

I'm seeing something kind of similar with services and I'm not sure if it's related or not. Working on figuring it out this morning

distant sandal
#

If you want to check out my repo and branch:

git clone git@github.com:sagikazarmark/daggerverse.git
cd daggerverse
git checkout helm
cd ci
dagger call helm

The failing tests are the last ones in ci/helm.go.

bronze bear
#

What I was running into yesterday is that a container or service with a dependent service couldn't resolve the hostname of the dependent service. Might be the same root cause. Will let you know

distant sandal
#

That's what I see, but in addition to that some commands also seem to fail that don't even use that service.

bronze bear
#

ok yeah i'm specifically hitting lookup 5r4dg8qetp2iq.r4mh9kocl49fi.dagger.local on 10.87.0.1:53: no such host only when I have a Sync() in the pipeline. Sounds like the same issue

distant sandal
#

Yep, I'm calling sync as well. Removing Sync is probably the only thing I haven't tried 🙂

bronze bear
#

Removing sync worked for me, although I haven't thought of a trick to get the thing I want to Sync to still exec