👋 @Erik Sipsma @vito Hey, I'm guessing | Dagger | Page 1

versed steeple Jun 3, 2025, 5:59 PM

#

guessing you tried and that doesn't work already? I feel like most of the low-level plumbing probably exists to support it, might just need to be hooked up in a few missing places?

#

going off memory, i'll double check

red violet Jun 3, 2025, 6:00 PM

#

oh wait, I'll try first

#

I just assumed

#

bold of me

#

(thought it would be wrapped into something different than an exec error)

versed steeple Jun 3, 2025, 6:03 PM

#

haha, looking at the relevant code there's a chance it might work already. The dockerfile code-paths are slightly different but when you RUN something I think it still ends up hitting these lines: https://github.com/sipsma/dagger/blob/129e0f14892718036f11497eea6ff28f001bf551/engine/buildkit/client.go#L175-L175

which is where the magic happens

#

(in WrapError)

red violet Jun 3, 2025, 6:05 PM

#

doesn't seem to get caught

versed steeple Jun 3, 2025, 6:09 PM

#

ah, it might be this? https://github.com/sipsma/dagger/blob/129e0f14892718036f11497eea6ff28f001bf551/engine/buildkit/ref.go#L353-L353

basically the exec-op created for a dockerfile RUN doesn't have the mount where we store stdout/stderr/exit-code, so then WrapError gives up on trying to annotate it with ExecError stuff

#

trying to change that would require hacking the dockerfile frontend to include extra rw mounts in the exec-op created for RUNs

#

so not sure what level of desperation you're at 🙂

red violet Jun 3, 2025, 6:12 PM

#

definitely BELOW that haha

versed steeple Jun 3, 2025, 6:14 PM

#

I'm admittedly going off just reading the code, if you want to confirm it's hitting that line I linked to above you could add some println debugging, just on the off chance i'm misreading/remembering

#👋 @Erik Sipsma @vito Hey, I'm guessing