2019-07-19 00:08:05 UTC - yihuaf: It's didn't error out. It's just took really 
long (40+ min in total for `./gradlew distDocker`) before I killed it. I then 
tried to run `docker build -t ow-utils 
/home/yihuaf/private/incubator-openwhisk/tools/ow-utils` which seems to be the 
command that it stucks on. Indeed this `docker build` command was taking really 
long. It constantly stuck on setting up python libs.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563494885054200?thread_ts=1563494885.054200&cid=C3TPCAQG1
----
2019-07-19 05:29:18 UTC - Sven Lange-Last: @Roberto Santiago is my 
understanding correct that you are able to `kubectl exec` into the invoker pod 
/ container and can successfully run `docker` commands without the error shown 
in the invoker log?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563514158055100?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 05:30:37 UTC - Sven Lange-Last: are you able to successfully use the 
`docker pull` and `docker run` commands from within the kube invoker pod / 
container?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563514237055300?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 05:32:05 UTC - Sven Lange-Last: i guess your invoker pod / container 
uses the same docker daemon and bsd socket file as kube itself? how exactly do 
you mount the socket file into your invoker pod / container? please share these 
parts of the kube manifest.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563514325055500?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 05:35:48 UTC - Sven Lange-Last: if kube uses docker to manage 
containers, the number of containers depends on the number of pods (no 
surprise…). a container is created for each init container and container 
defined in the pod manifest. in addition, a sandbox container is created for 
each pod. this sandbox container is created first and holds the pod’s 
namespaces and network interfaces. when the actual (init) containers are 
created, they inherit the namespaces of the sandbox container.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563514548055800?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 05:42:11 UTC - Sven Lange-Last: it looks like you are using gke - 
are you sure that your kube cluster uses docker for container management?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563514931056000?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 05:47:49 UTC - yihuaf: It seems to be calling pycompile. I'm running 
this on a laptop so it may just be the performance of pycompile. However, 
looking at the docker file, I can't seem to see the command that are calling 
the pycompile. Do `apt-get install` actually calls pycompile?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563515269056200?thread_ts=1563494885.054200&cid=C3TPCAQG1
----
2019-07-19 06:15:12 UTC - yihuaf: Once I build the ow-util image, everything 
else builds ok with `./gradlew distDocker`.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563516912056500?thread_ts=1563494885.054200&cid=C3TPCAQG1
----
2019-07-19 06:33:25 UTC - Roberto Santiago: @Sven Lange-Last Thanks for the 
feedback and questions.  I was travelling last night but will have a chance to 
investigate further later today.  I will get answers to your questions.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563518005056700?thread_ts=1563458366.047800&cid=C3TPCAQG1
----
2019-07-19 11:48:56 UTC - Satwik Kolhe: What is the job of "invoker-agent"?

I did not understand this "invoker-agent - worker node invoker agent -- used to 
implement suspend/resume on action containers for a remote invoker" 
(<https://github.com/apache/incubator-openwhisk-deploy-kube/blob/master/docker/README.md>)

Thank you.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563536936057800?thread_ts=1563536936.057800&cid=C3TPCAQG1
----
2019-07-19 11:58:44 UTC - chetanm: That is to support suspend and resume 
feature when cluster is configured to use `KubenetesContainerFactory`. In 
default mode it uses local `DockerContainerFactory`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563537524057900?thread_ts=1563536936.057800&cid=C3TPCAQG1
----
2019-07-19 11:59:26 UTC - chetanm: I also saw it took some time during initial 
days. Looks like thats a slow step
slightly_smiling_face : yihuaf
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563537566058100?thread_ts=1563494885.054200&cid=C3TPCAQG1
----
2019-07-19 12:09:31 UTC - Satwik Kolhe: Ohkye. Great. And what does "remote 
invoker" mean? Is it like an invoker pod running on a different k8s worker node?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563538171058300?thread_ts=1563536936.057800&cid=C3TPCAQG1
----
2019-07-19 12:17:38 UTC - chetanm: Yes in KCF (k8s container factory) mode 
there would a set of invoker pods running which would schedule action pods.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563538658058500?thread_ts=1563536936.057800&cid=C3TPCAQG1
----
2019-07-19 12:17:58 UTC - chetanm: It would use these invoker agent to suspend 
and resume
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563538678058700?thread_ts=1563536936.057800&cid=C3TPCAQG1
----
2019-07-19 12:21:48 UTC - Satwik Kolhe: Ohkye. So I should be reading about 
KCF. Thanks. Appreciate your help!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563538908058900?thread_ts=1563536936.057800&cid=C3TPCAQG1
----

Reply via email to