cloud furnace
I'm getting some errors publishing to ECR, and I'm trying to get some more detail on the manifest that it's building. Is there any way (short of exporting to tarball) to inspect the manifest that dagger is creating?
I think that the buildkit daemon might be adding provenance or sbom or something, but hard to determine what.
silver raven
You can output them to disk using AsTarball which should give you the OCI image equivalent so you can inspect it
I don't think it'll be provenance/sbom, dagger is actually not hooked up to capture and get any of that information (which is an entirely separate issue in itself)
cloud furnace
I wish ECR had more info on the failed upload :/
Just get
┃ │ │ │ xxxx:1.2.1-1aa05d2: failed to do request: Post \"https://xx.dkr.ecr.us-west-2.amazonaws.com/v2/service-xx/api-xx/blobs/uploads/\": EOF\n"
edgy trellis
Hey Steven! That's interesting since we publish images to ECR ourselves without issues. Any chance you can provide a repro?
Does it happen with all images?
edgy trellis
@cloud furnace have you checked if the engine logs has more information about it?
cloud furnace
sorry meant to circle back here... yeah basically not a dagger issue
ultimately something was wrong with my docker daemon. buildkit logs were showing "broken pipe", sometimes "out of space" - I just blasted the whole thing and restarted my computer and things ended up ok.
I had thought it was dagger issue b/c some builds were working, while others did not. probably some level of caching or different storage / networking requirements within the build that allowed some to go through and some not to