You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this discussion which I agree with the premise of, there is no way to have Distillery include 3rd party binaries in a release.
That leaves me needing to modify the runtime to include wkhtmltopdf with my project, and the latest available package for Ubuntu 16 is 0.12.2.4 and I require the latest, 0.12.5.
Although I'm not sure exactly how, it seems I should be able to create a custom Dockerfile from this runtime stack and use it as a custom runtime. It would be fantastic to understand how to accomplish this, but I haven't tried this route yet.
The hack I have in place for now is to do it with a nasty entrypoint. This is undesired for a multitude of reasons.
Thanks, @zeroasterisk. What I'm hearing is I could fork this repository, making necessary modification in, for example, within the Dockerfile generator template Dockerfile-release.eex and use runtime-build.sh to put this customized runtime into Google Storage for use by my project.
What is the opinion of adding a runtime_scripts section, similar to build_scripts? I know this project likely needs to follow a more generic app engine project template - but if the flexibility exists and it sounds like a good idea, I'd be happy to add it.
According to this discussion which I agree with the premise of, there is no way to have Distillery include 3rd party binaries in a release.
That leaves me needing to modify the runtime to include wkhtmltopdf with my project, and the latest available package for Ubuntu 16 is 0.12.2.4 and I require the latest, 0.12.5.
Although I'm not sure exactly how, it seems I should be able to create a custom
Dockerfile
from this runtime stack and use it as a custom runtime. It would be fantastic to understand how to accomplish this, but I haven't tried this route yet.The hack I have in place for now is to do it with a nasty entrypoint. This is undesired for a multitude of reasons.
Is there currently a better way to accomplish this that wouldn't require creating a custom runtime?
The text was updated successfully, but these errors were encountered: