fresh bear
Currently getting this message when I use the Wolfi module and nodejs (any version):
node: /usr/lib/libm.so.6: version `GLIBC_2.43' not found (required by node)
As per https://support.chainguard.dev/hc/en-us/articles/46374554648859-Glibc-2-43-Release-Impact-on-apk-add-and-Chainguard-Images, this is caused by a mix of an old base image and a new package. I'm not sure how that's possible, given that the Wolfi module essentially uses apko to build the image.
cinder shore
Currently getting this message when I use the Wolfi module and `nodejs` (any ver...
👋 this seems to work for me
dagger -vvv -m github.com/dagger/dagger/modules/wolfi call container --packages=nodejs with-exec --args="node,-e,console.log('hello world')" stdout
are you using the same Wolfi module by any chance?
fresh bear
I am using the tagged 0.20.1 wolfi from that repository
cinder shore
I am using the tagged 0.20.1 wolfi from that repository
strange.. does it work if you run the same snippet I've shared above?
fresh bear
Strangely, yes.
fresh bear
Managed to reproduce it in an open-source PR: https://github.com/moosingin3space/sun-api/actions/runs/23412756042/job/68103100059?pr=139
fresh bear
Dagger Cloud trace: https://dagger.cloud/moosingin3space/traces/2c8b5932e19d034f28f1401752d800f6
cinder shore
Managed to reproduce it in an open-source PR: https://github.com/moosingin3space...
seems like you managed to get it working by updating deps?
I was just checking into this when I saw a commit in your PR
fresh bear
Yes, I just got that working with a Claude Code debugging session!
cinder shore
Yes, I just got that working with a Claude Code debugging session!
probably an update in wolfi was not being compatible with some other packages