#Welcome The slowness might be called by

1 messages · Page 1 of 1 (latest)

zealous juniper
#

here's the code from the step i'm currently on

import Client, { connect } from "@dagger.io/dagger"

// initialize Dagger client
connect(async (client: Client) => {
  // get Node image
  // get Node version
  const node = client.container().from("node:16").withExec(["node", "-v"])

  // execute
  const version = await node.stdout()

  // print output
  console.log("Hello from Dagger and Node " + version)
})

here's the link: https://docs.dagger.io/sdk/nodejs/783645/get-started

Get Started with the Dagger Node.js SDK | Dagger

Introduction

#

re logging i've tried the following env variables i found somewhere else in the docs without any luck:

export DAGGER_LOG_FORMAT="plain"
export DAGGER_LOG_LEVEL="trace"

terse vigil
#

there’s an argument you can pass to connect to configure a log output

zealous juniper
#

ahh thank you

#

which tipped me off that i should be getting more in the logs

#

Okay i have logs now which his nice:

weirdly the bulk of the delay seems to be from before connecting with the engine

image.png
terse vigil
#

this is not expected, would you mind filing an issue?

#

it may be caused by the auto-install logic. The client library will check for a running or out-of-date engine and if not there, will download it automatically. You may be experiencing an issue with that feature

zealous juniper
#

that could be. i think i installed a version of the engine last summer