To workaround, instead of localhost, you’d have to use another special domain provided by Docker to connect to your computer’s localhost instead of the container’s. You can consult Docker’s documentation to find about it depending on the operative system you use (Windows, MacOS or Linux)
Thank you for the suggestion.
I had thought that because the data was visible in the browser using the URL with port 8080, that was ruling out any issues with port 8080.
Also, on a page I have an API Data Source using a similar URL to the same service on 8080 that populates a Bootstrap table fine. The setup of the API Action above seems to have all the same settings as the API Data Source but just doesn’t work.
It works for you from the editor because the editor is outside of docker and goes directly to your localhost:8080.
But when you run it from the code, that is being done inside of docker and thus is not reaching the localhost of your computer, it is reaching the localhost of the docker container.
Sorry, I wasn’t clear. My idea (I have not tried this) was that you would replace localhost:8080 with host.docker.internal:8080 in the URL of your API Action.