Port configuration | Dagger | Page 1

balmy leaf Nov 20, 2024, 5:41 AM

#

@broken adder can I ask what your use case is? The Dagger API served by dagger listen is not meant to be accessed remotely. Depending on what you're trying to achieve, we can point you in the right direction.

broken adder Nov 20, 2024, 3:19 PM

#

i'm trying to set up a dagger runner on a dedicated machine that local/ci clients can talk to, which will build up a persistent cache over time

broken adder Nov 20, 2024, 3:41 PM

#

to be clear what i ended up trying was something like

docker run -it -u root --privileged -p 32771 registry.dagger.io/engine --addr tcp://127.0.0.1:32771

but wasn't able to then connect using the _EXPERIMENTAL_DAGGER_RUNNER_HOST var with the same address- just hangs (same machine)

#

i'm probably misunderstanding something bigly

balmy leaf Nov 20, 2024, 4:06 PM

#

try -p 32771:32771 ?

broken adder Nov 20, 2024, 4:19 PM

#

same thing, connecting to engine...

last jackal Nov 20, 2024, 6:15 PM

#

@broken adder are you able to get it to work with tcp://0.0.0.0:32771?

broken adder Nov 20, 2024, 6:17 PM

#

that did it! ugh should have tried that

#

why exactly is that an issue?

balmy leaf Nov 20, 2024, 6:22 PM

#

it's a container thing. listening on localhost means your app is only reachable within the container

#

sorry I missed that in your initial message

#Port configuration