need a way to provide user w/pre-cached builds

[eyberg]

some initial guidance:

• create a 'packages' subfolder in google cloud that can house a package

(i'd just default to this schema for now: https://hub.docker.com/_/node )

I'd just start by uploading one like barebones php and then we can start working out the kinks

now that php is 'working'

nanovms/nanos#219
nanovms/nanos#143

we'll want to provide some pre-made images for the end-user - for things like interpreters/databases/etc.. - basically things that we won't expect the user to provide in the future (and it also makes support way the hell easier)

open /etc/ld.so.cache - not found
open /lib/x86_64-linux-gnu/tls/libresolv.so.2 - not found
open /lib/x86_64-linux-gnu/libxml2.so.2 - not found
open /usr/lib/x86_64-linux-gnu/tls/libxml2.so.2 - not found
open /lib/x86_64-linux-gnu/libssl.so.1.1 - not found
open /lib/x86_64-linux-gnu/libcrypto.so.1.1 - not found
open /lib/x86_64-linux-gnu/libicui18n.so.57 - not found
open /lib/x86_64-linux-gnu/libicuuc.so.57 - not found
open /lib/x86_64-linux-gnu/libicudata.so.57 - not found
open /lib/x86_64-linux-gnu/libstdc++.so.6 - not found
nosyscall set_robust_list
nosyscall madvise
open /etc/localtime - not found
open /etc/php/7.0/cli/php-cli.ini - not found
open /etc/php/7.0/cli/php.ini - not found
open /etc/php/7.0/cli/conf.d - not found

for instance there's a few /etc files that should be present, a few libs, etc.

I don't have a strong direction here but by looking at the old mcp 'new image creation' UI you can see we provide common env vars, tls certs, etc.

I'm thinking if you set a variable in the config.json like 'lang: php7' or something like that instead of loading a binary up locally that'd be a cue for us to slurp down a known working image

one of the things that was brought up earlier was that right now we don't? have the capacity of splitting the image itself up? like - common known/needed files vs user contributed stuff?

[eyberg]

so case in point - trying out a simple curl in php - typically you'd have a devops person apt-get install this, edit the php.ini, etc. - we want to provide an out of the box exp for the end-user - we should err on the side of including everything for their project and if they want a more slimmed-down interpreter that's bare bones they can build it themselves

[eyberg]

closing for now