#Dep scanner

1 messages · Page 1 of 1 (latest)

clever urchin
#

Possibly! What would the output be, though -- are you thinking it would just build an image containing the deps?

mighty vessel
#

I was thinking that by default, it would write the stripped directory to the specified path on the local filesystem?

#

With options to export to an image, push to a registry, perhaps even push to a remote git repo... (all easy to implement with dagger)

clever urchin
#

Oh yeah, it could do that

#

Would that be useful, though?

#

I suppose that with an image export you could use it as a base for building another image, but I'm wondering if you had something else in mind

mighty vessel
#

I was wondering how to package your project in the optimal way for maximum adoption, beyond people who already know and love Dagger

#

And more generally, I'm thinking of possible tools that could be useful and successful standalone, where building them on top of a dagger SDK is a competitive advantage because it makes normally difficult things much easier

#

As a CLI tool, couldn't it be used by executing it in a Dockerfile?

clever urchin
#

Yeah, I guess it could. My instinctive thought was that it wouldn't be useful as a cli because you have to import full file trees as dependencies early in the dockerfile to allow you to use the cli. But you can get around that with multi stage builds

#

Otoh anecdotally I've found most docker users don't really get multi stage builds or the power of them for caching, so there's some education that's required there

#

Tangentially, I think one reason I'm excited about dagger is that it functions as a bit of a reset on that. The sdk centers things that buildkit could do but weren't obvious or easy. It emphasizes the fact that you're working with graphs, not with... towers? I think that's how most people see images. They're linear, and if you take one brick out everything above it has to fall too

mighty vessel
#

towers 😄