jebruen opened a new issue #5201:
URL: https://github.com/apache/openwhisk/issues/5201


   Can someone please explain the following? 
   
   "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."
   
   When I update and invoke an action with a publicly available image on 
dockerhub using the --docker flag, I would expect that image to be shown when I 
do a "docker image ls," but I don't see it. Where are these images cached 
locally? 
   
   And I would assume that future invocations using that same image defined 
with --docker would be constructed from the local copy of the image; is that 
right?
   
   <!--
   We use the issue tracker for bugs and feature requests. For general 
questions and discussion please use https://openwhisk.apache.org/slack.html or 
https://openwhisk.apache.org/community.html instead.
   
   Do NOT share passwords, credentials or other confidential information.
   
   Before creating a new issue, please check if there is one already open that
   fits the defect you are reporting.
   If you open an issue and realize later it is a duplicate of a pre-existing
   open issue, please close yours and add a comment to the other.
   
   Issues can be created for either defects or enhancement requests. If you are 
a committer than please add the labels "bug" or "feature". If you are not a 
committer please make clear in the comments which one it is, so that committers 
can add these labels later.
   
   If you are reporting a defect, please edit the issue description to include 
the
   information shown below.
   
   If you are reporting an enhancement request, please include information on 
what you are trying to achieve and why that enhancement would help you.
   
   For more information about reporting issues, see
   
https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#raising-issues
   
   Use the commands below to provide key information from your environment:
   You do not have to include this information if this is a feature request.
   -->
   
   ## Environment details:
   
   * local deployment, native ubuntu, Mac OS, Kubernetes, ...
   * version of docker, ubuntu, ...
   
   ## Steps to reproduce the issue:
   
   1.   
   2.   
   3.   
   
   
   ## Provide the expected results and outputs:
   
   ```
   output comes here
   ```
   
   
   ## Provide the actual results and outputs:
   
   ```
   output comes here
   ```
   
   ## Additional information you deem important:
   * issue happens only occasionally or under certain circumstances   
   * changes you did or observed in the environment
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to