#Why am I seeing this error "ERR failed to emit telemetry error="traces export: context deadline exce
1 messages ยท Page 1 of 1 (latest)
๐ by any chance are you running your pipelines in a restricted enviroment of some sort?
Sorry @tacit nimbus I was away last week.
Yes, I'm running this behind the company VPN. I've managed to get a custom dagger engine working (with custom CA and GOPROXY). Any pointers how to debug this further would help me a lot.
I think i solved the issue.
my environment variables
export DO_NOT_TRACK=1 # disable dagger metrics
export NOTHANKS=1 # disable dagger cloud
export GOAWAY=1 # disable dagger traces
export DAGGER_ENGINE_IMAGE=$(dagger version | rg -o "\(([^)]+)\)" | sed 's/[()]//g')
export DAGGER_VERSION=$(dagger version | rg -o 'v\d+\.\d+\.\d+' | head -1)
export _EXPERIMENTAL_DAGGER_RUNNER_HOST="docker-container://custom-dagger-engine-$DAGGER_VERSION"
export _EXPERIMENTAL_DAGGER_CLI_BIN="$(which dagger)"
My custom dagger engine:
docker run \
--rm \
--privileged \
--name "custom-dagger-engine-$DAGGER_VERSION" \
--env _DAGGER_ENGINE_SYSTEMENV_GOPROXY='...' \
--volume "/var/lib/dagger" \
--volume "$PWD/engine.toml:/etc/dagger/engine.toml" \
--volume "$PWD/certs:/usr/local/share/ca-certificates" \
$DAGGER_ENGINE_IMAGE
Awesome, I'm glad that you managed to figure it out ๐
Having said that, seems like you've disabled cloud altogether, is that intended?
Yeah, for now at least. Need to get first some prototypes working and only than try to figure out how to convince IT to either open our VPN or get an on prem solution. You know small steps, small "injuries" ๐