Eran Duchan

Thank you for the extremely detailed report! I can't provide an ETA for this, but once we prioritize the MQTT trigger we'll definitely take a look. Of course, any contribution...

I was unable to reproduce this with the following steps: 1. Run dashboard: ``` docker run -p 8070:8070 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp quay.io/nuclio/dashboard:1.1.1-amd64 ``` 2. Create a Python function with...

When you invoke through the dashboard, the invocation request is proxied through the dashboard service to the function. This is to prevent direct communication between your browser and the function...

Addressed by #962. Awaiting feedback

Just so I understand - you're still running everything on Kubernetes?

The fix was for k8s. I don't exactly understand why the dockerized dashboard can't access `172.17.0.1:42975` - using the docker bridge interface address has worked for us over the years,...

> Ok at first, I upgraded nuclio on our K8S cluster and dashboard can now execute functions: wow nice, thanks ! 👍 > Would you like I create a new...

Thanks for the feedback @AdrianLsk. We'd love a contribution for this as currently our backlog does not include improvements to the PubSub trigger, even though your suggestions make 100% sense....

Please note that (as far as I understand) nvidia-docker was folded into Docker at 19.03. From https://github.com/NVIDIA/nvidia-docker#quickstart: > Note that with the release of Docker 19.03, usage of nvidia-docker2 packages...

@mhe-wyze It should not work out of the box, this parameter is only used in k8s. Which Docker version are you using?