intergate a small backend server with existing pushpin Docker file

[bharath-naik]

Running pushpin Docker as a container works fine as standalone.
Now i am trying to add a small nodejs banckend application to the existing pushpin Dockerfile so that i can set headers and also acts as a reverse proxy for pushpin. but as the Dokcerfile has the limitation of single CMD command i cannot run the node server command once again in the same Dockerfile. eg: CMD ["pushpin", "--merge-output"]. how can i solve this.

[jkarneges]

Hi,

It's best to run separate containers if you can. This is typically how containerized deployments are done. It's also a good way to deploy Pushpin, because multiple backend instances may need to share the same Pushpin instances.

But if you really need to run multiple programs in one container, you can use something like supervisord as the main CMD.

[bharath-naik]

Thanks @jkarneges. it helped
I have created pushpin and backend containers and deployed in GKE with istio(service mesh) and in the routes file of pushpin container, I have given as mbackend1-service.default.svc.cluster.local:8000/* while accessing the 7999 port from the browser it says No route for host: 1xx.1xx.1xx.4.
Does routes file accept only DNS and IP address only or will it also accept the service urls like service-name.namespace.cluster.local

[jkarneges]

Pushpin uses DNS lookups to resolve targets, so service URLs should work.