2022-02-11 10:40:26 UTC - David Williams: I want to install OpenWhisk into Ubuntu 20. I got the following error: > Task :common:scala:distDocker FAILED Fri Feb 11 17:28:51 CST 2022: Command 'docker build -f /homeatform/openwhisk/common/scala/Dockerfile -t scala /homeatform/openwhisk/common/scala' was killed after 840 seconds, no more retries left, aborting... Error response from daemon: No such image: scala:latest Error response from daemon: No such image: scala:latest Error response from daemon: No such image: scala:latest
> Task :common:scala:tagImage FAILED Fri Feb 11 17:28:51 CST 2022: Executing 'docker tag scala whisk/scala:latest' Fri Feb 11 17:28:51 CST 2022: Command 'docker tag scala whisk/scala:latest' failed with exitCode 1, 2 retries left, retrying... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644576026801249?thread_ts=1644576026.801249&cid=C3TPCAQG1 ---- 2022-02-11 10:44:37 UTC - David Williams: Any help will be appreciated. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644576277966469 ---- 2022-02-11 18:02:00 UTC - Brendan Doyle: This is probably going to warrant an email, but if you have not upgraded to akka 2.6 yet in your clusters please read. The default remoting protocol for akka changes in akka 2.6 to artery. This is handled gracefully in the repo's default ansible deployment. However, if you're not using the default ansible deployment; this will break your controller cluster with the upgrade. Two things you need to do: 1. Turn off artery with `akka_remote_artery_enabled=false` 2. Change the config paths of all of your netty configs to include `classic` i.e. `akka_remote_classic_netty_tcp_hostname` More can be found here in the classic remoting documentation: <https://doc.akka.io/docs/akka/current/remoting.html#configuration> Also netty will be removed with akka 2.7 so you'll have to upgrade to artery at some point. If you're using the default ansible deployment this should already be handled. Back when akka 2.6 was first released there were quite a few bugs in artery so we stuck with netty in our services, although I'm guessing that's no longer a problem. Lastly, this went undetected by us for a couple weeks since the controller node is still able to start without being able to form the cluster. Each controller then just acts as it's own cluster overprovisioning the invokers and not distributing namespaces' limits. I'm going to send out a pr adding some logs when nodes are added or removed to the cluster and a metric for current cluster size viewed by each controller. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644602520275979?thread_ts=1644602520.275979&cid=C3TPCAQG1 ---- 2022-02-11 21:11:39 UTC - Matt Welke: Trying to make a Micronaut native image for OpenWhisk. I have the following for my init controller: ```@Controller("/init") public class InitController { @Post @Consumes(MediaType.APPLICATION_JSON) @Produces(MediaType.TEXT_PLAIN) public String init() { return ""; } }``` But I'm getting an error when I try to run it: ```{ "error": "The action failed during initialization: {\"message\":\"Unsupported Media Type\",\"_links\":{\"self\":{\"href\":\"/init\",\"templated\":false}},\"_embedded\":{\"errors\":[{\"message\":\"Content Type [application/json] not allowed. Allowed types: [text/plain]\"}]}}" }``` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644613899366329 ---- 2022-02-11 21:12:19 UTC - Matt Welke: The reason my init handler is so bare bones is because I figure it doesn't have to do anything. The plan is for my Java code to just go into the run controller, with nothing happening in the init controller. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644613939186089 ---- 2022-02-11 21:12:24 UTC - Matt Welke: Anyone have any experience with this? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644613944151929 ---- 2022-02-11 22:01:01 UTC - Matt Welke: complete app: <https://github.com/mattwelke/micronaut-native-openwhisk-test> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1644616861260909 ----
