This message was deleted.
# epinio
a
This message was deleted.
m
Maybe @broad-dream-81849 has an opinion?
And a thing we’re running into, is that we’re creating a ‘build’ directory and only that needs to be deployed, not figured out how to strip the rest.
b
absolutely, you should go with whatever best fits your need. If you already have a Docker image you can skip completely the staging part, and use Epinio for everything else. Or you can provide a different builder, that will work better in your case
h
There is an initiative upstream to allow dockerfiles to be used in the buildpack flow which will bridge the two worlds. Also, the default buildpacks are quite heavyweight as they are trying to solve for everything. It's not too difficult to build your own buildpack that builds much more lightweight images (figuring out the documentation is the hard part...)
b
I agree, we have build our own buildpack from paketo ones becos some of them are full of vulnerabilities that is not fix in time
it is not difficult but need some team member to be patient to RTFM.
m
@high-morning-12231 Any reference to that, github issues or something that you know by any chance?
h
Here is the RFC discussing the new functionality: https://github.com/buildpacks/rfcs/issues/224
Reading through the current status of that RFC, I think this might already be doable with what's in the box. I just don't know what would be needed to make it go. I might play with it over the weekend...