Rodric, are you running a custom api gateway container ? The lines at [1] should fix the issue for you.
NGINX has its own internal DNS resolution for performance considerations. I'm curios what the content of "/etc/api-gateway/conf.d/includes/resolvers.conf" is inside the apigateway container. Also, in case you use a custom configuration file for OW, it's possible that the config doesn't include "resolvers.conf" and hence the DNS resolution doesn't work ? [1] - https://github.com/apache/incubator-openwhisk-apigateway/blob/master/init.sh#L58-L59 On Wed, Jun 26, 2019 at 5:28 PM Rodric Rabbah <rod...@gmail.com> wrote: > I tried to use the api gateway with the standalone controller and ran into > a few issues which I'll document in the relevant docs soon. I'm now hitting > an issue where the api gateway cannot resolve the host for routing a > request. > > I opened > https://github.com/apache/incubator-openwhisk-apigateway/issues/345 > to summarize the findings. I created an API successfully which when I curl > fails in the gateway because it can't resolve the upstream host. > > I can nslookup/ping the stanalone controller from the api gateay container, > and I can successfully the webaction URL from the api gateway container as > well. > > How does the API gateway resolve a hostname and where is that code? Thanks > for the help. > > -r >
