#👋 Random question.
tribal lichen
willow epoch
Hey @tribal lichen. @hot viper (colleague) has come with a workaround to add labels and hack something up when exporting the tarball using the above approach 😉
Thanks!
copper vapor
@willow epoch can you elaborate on the workaround if you don't mind? I am curious
high verge
I'd assume they're manually modifying the extracted tarball and adding the RepoTags to the manifest there. The main reason why Dagger doesn't support adding those RepoTags natively is because RepoTags is currently a docker specific thing and not part of the OCI spec: https://github.com/opencontainers/image-spec
willow epoch
We have makefile on top of dagger, 90% of the targets are simply dagger call xxxx
The function of our module that builds the container and returns a *dagger.Container is now adding labels as the post above explains, and we do some gluing with make... do read the exported container sha, retrieve it and use docker to move the labels to tags (Marcos is right, outside dagger)
It does the trick of "I've built a docker image and I can run it locally"
Our users know docker and don't know any dagger (yet!). So making them use dagger while not forcing them to learn it is challenging.e
high verge
move the labels to tags (Marcos is right, outside dagger)
it should be possible to do all this within Dagger also. This way, if the makefile currently runs some funky commands, you can avoid it and keep the full portability of the pipeline
copper vapor
it should be possible to do all this within Dagger also
That's what I was thinking when I read that. Most things you can do with a makefile you can do with dagger also