2022-03-17 21:23:00 UTC - Jacqueline Bruen: "Custom runtime images will be 
pulled from Docker Hub into the local platform registry upon the first 
invocation. This can lead to longer cold-start times on the first invocation 
with a new or updated image. Once images have been pulled down, they are cached 
locally." QUESTION: Where are these cached locally? I don't see the images when 
I do "docker image ls"
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1647552180645639
----
2022-03-17 21:29:39 UTC - Matt Welke: My understanding is that this is 
describing using Kubernetes as the platform upon which you deploy OpenWhisk, 
and that therefore the default behavior of Kubernetes is taken advantage of 
here, where the cluster nodes each contain a cache of pulled images. So 
OpenWhisk is relying on that behavior and counting on those caches to be hit.
white_check_mark : Rodric Rabbah
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1647552579925739
----
2022-03-17 23:48:35 UTC - Jacqueline Bruen: I got the above quote from 
<https://github.com/apache/openwhisk/blob/master/docs/actions-docker.md|here>, 
which is from the docs of the vanilla deployment of OpenWhisk. I am just trying 
the locate the directory where these images are cached because "docker image 
ls" isn't picking them up.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1647560915981059
----

Reply via email to