2020-10-24 14:56:36 UTC - Michele Sciabarra: Hello Whiskers I have a question about Invokers. Is it possible to tag a runtime to be executed only in certain invoker nodes? My use case is to be able to run an action in a node with a GPU. I would have a few Invoker nodes with GPU but not all. So I am wondering if it is possible in some way currently to annotate/tag or in other ways make sure a given invoker will pick an action and others not all. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603551396137600?thread_ts=1603551396.137600&cid=C3TPCAQG1 ---- 2020-10-24 15:07:11 UTC - Dominic Kim: I believe that is not possible in the current code base. You can add that feature by adding some resource tag in the invoker health message and make controllers to filter invokers based on the given tag. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603552031139700?thread_ts=1603551396.137600&cid=C3TPCAQG1 ---- 2020-10-24 15:08:11 UTC - Dominic Kim: We internally implemented that feature but our code base is based on the new scheduler. I think you can use the feature when the scheduler contribution is done. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603552091141300?thread_ts=1603551396.137600&cid=C3TPCAQG1 ---- 2020-10-24 19:02:37 UTC - Alessandro Banfi: Hi everyone, I'm trying to execute without success a golang action on OpenWhisk standalone. When I invoke the action the following error is displayed `"error": "Cannot start action. Check logs for details."` Looking into the logs I found the following line `[ERROR] [#tid_sid_unknown] [ContainerProxy] Failed during init of cold container Some(ContainerId(c17bde1123b801aa392b446ab406211d2d51e792b576de3f53c69eaf79c49cc1)), queued activations will be aborted.` just after the attempt to start the container. Where can I look in order to understand which is the issue? How can I fix it? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603566157145000?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:04:12 UTC - Alessandro Banfi: It is worthwhile to mention that golang actions via the playground are working as expected, I obtain the following issue only invoking actions added with wsk. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603566252146300 ---- 2020-10-24 19:21:49 UTC - Rodric Rabbah: this suggests a problem compiling the code https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603567309146500?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:22:04 UTC - Rodric Rabbah: how are you creating the action https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603567324146700?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:35:18 UTC - Alessandro Banfi: I tried both with `wsk -i action create main main.zip --main main --docker openwhisk/action-golang-v1.15` and with `wsk action create main main.go` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603568118146900?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:36:58 UTC - Alessandro Banfi: The first command has been executed after the compilation performed inside of the openwhisk/action-golang-v1.15 container as reported in the go rntime repo and the second one starting from what is stated into the openwhisk standalone repo. Both treid without success ... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603568218147100?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:57:26 UTC - Alessandro Banfi: @Rodric Rabbah after trying with the example reported into OpenWhisk repo docs I found out it worked as expected, as you stated the issue should be in my source code https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603569446147300?thread_ts=1603566157.145000&cid=C3TPCAQG1 ---- 2020-10-24 19:57:35 UTC - Alessandro Banfi: thanks for your support! +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603569455147500?thread_ts=1603566157.145000&cid=C3TPCAQG1 ----
