2019-06-20 01:14:59 UTC - Rodric Rabbah: Just read the blog @rawkintrevo. Very cool I’d like to try this out.
Note that “OpenWhisk expects its Docker functions to start off from the dockerSkelaton image.” isn’t quite right. You can use any image as your base as long as you implement the lifecycle/protocol. What you get from the skeleton is a built in solution. You could have started with our python image or otherwise. +1 : rawkintrevo https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1560993299081500?thread_ts=1560993299.081500&cid=C3TPCAQG1 ---- 2019-06-20 01:15:20 UTC - Rodric Rabbah: @James Thomas you wanted to nuke the skeleton related parts of the cli. I can’t remember if we’ve done that already. +1 : Carlos Santana https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1560993320082300?thread_ts=1560993320.082300&cid=C3TPCAQG1 ---- 2019-06-20 08:59:15 UTC - James Thomas: we have not - I totally forgot about that https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561021155083500?thread_ts=1560993320.082300&cid=C3TPCAQG1 ---- 2019-06-20 14:24:46 UTC - rawkintrevo: I updated w your comment verbatum. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561040686083900?thread_ts=1560993299.081500&cid=C3TPCAQG1 ---- 2019-06-20 14:24:55 UTC - rawkintrevo: thanks for the note https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561040695084100?thread_ts=1560993299.081500&cid=C3TPCAQG1 ----
