Richard Gee

Derek add label: PR

# Happy Path Check currently running tasks: ``` $ sudo ctr -n openfaas-fn task ls TASK PID STATUS nodeinfo 3914 RUNNING env 4056 RUNNING derek-sha256 4452 RUNNING ``` Lets `rm...

Edit: Further investigation meant a rerun was required. Rerun results provided here. Putting the 0.14.3 binary back in place and rerunning the N=1000 test: ``` $ time ./loop.sh Attempting scale...

Following the steps of @tmiklas I've found that that error corresponds to a HTTP/500. So far I've only found `Can't reach service for:` here: https://github.com/openfaas/faas-provider/blob/bc0f26cae70c1b3ba2a595cea8bfb8c04925d5c6/proxy/proxy.go#L168-L168 Which is introduced in this...

I ought to mention that the same happens for me using 0.14.3: ``` root@derek:~# faasd version __ _ / _| __ _ __ _ ___ __| | | |_ /...

I can also trigger the HTTP/404 in this way, again on 0.14.3: ``` killall -9 faasd; systemctl restart faasd root@derek:~# ctr -n openfaas-fn task ls TASK PID STATUS nodeinfo 3914...

Derek close: addressed in #172

If I'm interpreting your set-up correctly, I would be interested in what happens if you add a `docker pull registry.gitlab.com/vnourdin/my-project/my-function` between the ~build~ push and deploy steps.

I was thinking more about the CI/CD steps. You're clearly (now) working interactively. Does this look similar? https://github.com/alexellis/faas-containerd/issues/28

Derek close: Added in e778a3a6ded22fef3a28e78e28d5dc33f0d17dfd