1 - Follow the instructions from the README on a Ubuntu 18 VM running on OpenSUSE
2 - After running the job faas.hcl check that there is nothing on port 8080. You can't access through the browser nor with curl or ping.
3 - check with sudo docker ps that there is no container mapped to port 8080
4 - check that the port 8080 is not being used by any other process or service with sudo lsof -i -P -n | grep LISTEN
5 - check on Consul UI that Gateway is not listed and everything is Healthy. Also, it sometimes appears and disapears (WHY?)
6 - check the stderr logs for the gateway task are complaining only about nats not available, when it is available:
What happens?
The faas.hcl is not throwing any errors and the container does not start on port 8080
What were you expecting to happen?
The Open faas gateway should be running on port 8080. So I could deploy my function or access the UI.
Obs: On Consul UI I was seeing Gateway service appearing and disapearing. Why?
What are the steps to reproduce this issue?
1 - Follow the instructions from the README on a Ubuntu 18 VM running on OpenSUSE 2 - After running the job faas.hcl check that there is nothing on port 8080. You can't access through the browser nor with curl or ping. 3 - check with
sudo docker psthat there is no container mapped to port 80804 - check that the port 8080 is not being used by any other process or service with
sudo lsof -i -P -n | grep LISTEN5 - check on Consul UI that Gateway is not listed and everything is Healthy. Also, it sometimes appears and disapears (WHY?)
6 - check the stderr logs for the gateway task are complaining only about nats not available, when it is available:
What happens?
The faas.hcl is not throwing any errors and the container does not start on port 8080
What were you expecting to happen?
The Open faas gateway should be running on port 8080. So I could deploy my function or access the UI.
Obs: On Consul UI I was seeing Gateway service appearing and disapearing. Why?
Additional Information
Ubuntu, Docker, Nomad and Consult versions: