#yes I htink it s the build itself but

1 messages · Page 1 of 1 (latest)

late vigil
#

you're initializing the engine with the logger, correct?

#

let's continue here @copper topaz

#

so we don't spam the channel

copper topaz
#

suer

# 
time="2023-03-22T13:39:40Z" level=info msg="auto snapshotter: using overlayfs"
time="2023-03-22T13:39:40Z" level=warning msg="using host network as the default"
time="2023-03-22T13:39:40Z" level=info msg="found worker \"agbhu3u597s6rkcp8xtrh4901\", labels=map[org.mobyproject.buildkit.worker.executor:oci org.mobyproject.buildkit.worker.hostname:40f4776713f5 org.mobyproject.buildkit.worker.network:host org.mobyproject.buildkit.worker.oci.process-mode:sandbox org.mobyproject.buildkit.worker.selinux.enabled:false org.mobyproject.buildkit.worker.snapshotter:overlayfs], platforms=[linux/amd64 linux/amd64/v2 linux/amd64/v3 linux/386]"
time="2023-03-22T13:39:40Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
time="2023-03-22T13:39:40Z" level=info msg="found 1 workers, default=\"agbhu3u597s6rkcp8xtrh4901\""
time="2023-03-22T13:39:40Z" level=warning msg="currently, only the default worker can be used."
time="2023-03-22T13:39:40Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
time="2023-03-22T13:41:21Z" level=error msg="/moby.buildkit.v1.frontend.LLBBridge/StatFile returned error: rpc error: code = Canceled desc = failed to load LLB: context canceled"```
#

is it posible to make the engine log level more verbose?

#

I didnt start the egine myself tbh

#

I initiate the client, and I think it start automatically

late vigil
#

what do you get if you run this?

docker exec $(docker ps -q --filter name=dagger-engine-)  cat /etc/dagger/engine.toml
copper topaz
# 
docker exec $(docker ps -q --filter name=dagger-engine-)  cat /etc/dagger/engine.toml
root = "/var/lib/dagger"```
late vigil
#

ok, interesting. What SDK version are you using?

#

I think you're not running the latest engine which comes with debug logs enabled by default

copper topaz
#

in fact 0.3.2

#

I will retry with the 0.4.1

late vigil
#

please.. LMK how that goes

#

lots changed since 0.3.2

copper topaz
# 
docker exec $(docker ps -q --filter name=dagger-engine-)  cat /etc/dagger/engine.toml

debug = true
insecure-entitlements = ["security.insecure"]
#

so now, I have one more line

#2 [internal] load metadata for docker.io/library/debian:bullseye-slim
#2 DONE 1.9s

#3 importing cache manifest from dagger:10686922502337221602
#3 DONE 0.0s```

then it stayu for la long time 

and the engine logs says

...
time="2023-03-22T14:56:47Z" level=debug msg="healthcheck completed" actualDuration=1.122676ms spanID=c8f6aaa1c480f233 timeout=30s traceID=7b57e833f0d6708619ef2d1563f66079
time="2023-03-22T14:56:50Z" level=debug msg="healthcheck completed" actualDuration="338.006µs" spanID=8321604fe9da03db timeout=30s traceID=45a9cdd084ebfca708ef20571af48f34
time="2023-03-22T14:56:52Z" level=debug msg="healthcheck completed" actualDuration="979.393µs" spanID=c8f6aaa1c480f233 timeout=30s traceID=7b57e833f0d6708619ef2d1563f66079
time="2023-03-22T14:56:55Z" level=debug msg="healthcheck completed" actualDuration="292.162µs" spanID=8321604fe9da03db timeout=30s traceID=45a9cdd084ebfca708ef20571af48f34
time="2023-03-22T14:56:57Z" level=debug msg="healthcheck completed" actualDuration=1.105039ms spanID=c8f6aaa1c480f233 timeout=30s traceID=7b57e833f0d6708619ef2d1563f66079
time="2023-03-22T14:57:00Z" level=debug msg="healthcheck completed" actualDuration="317.039µs" spanID=8321604fe9da03db timeout=30s traceID=45a9cdd084ebfca708ef20571af48f34
time="2023-03-22T14:57:02Z" level=debug msg="healthcheck completed" actualDuration="953.116µs" spanID=c8f6aaa1c480f233 timeout=30s traceID=7b57e833f0d6708619ef2d1563f66079
time="2023-03-22T14:57:05Z" level=debug msg="healthcheck completed" actualDuration="264.649µs" spanID=8321604fe9da03db timeout=30s traceID=45a9cdd084ebfca708ef20571af48f34
time="2023-03-22T14:57:07Z" level=debug msg="healthcheck completed" actualDuration="896.042µs" spanID=c8f6aaa1c480f233 timeout=30s traceID=7b57e833f0d6708619ef2d1563f66079
...

#

and this time="2023-03-22T14:55:17Z" level=debug msg="unsupported cache type , defaulting to noop"

late vigil
#

so we can troubleshoot together

copper topaz
#

sure

late vigil
#

cc @robust river @charred tulip since you worked on this one. Did we hit a dead end here given the LLB resolving performance?

robust river
late vigil
copper topaz
#

So, i'm confirming that reducing the numbers of mounted_dir reduce the time of the execution