Websockets on Heroku Container Stack - docker

I am able to develop a websocket host on localhost but unable to connect when deployed to Heroku. I'm using the Heroku Container Stack for a docker image and can't find anything in their docs about websockets on this stack (unlike node, nginx, go, etc which all have examples in the docs). Can you not deploy a websockets in a container on Heroku. And if so how do you have to specify in the Heroku.yml file?
I tried to connect using postman and was expecting to connect the same way that I would if it was on localhost.

Related

building dockerized reverse proxy for and enviroment im working on

I currently have a small cluster of wordpress services implemented using docker, which are accessible through a nginx, using vhost for it and also the service is accessible over the internet using duckdns.org. The nginx server is not on docker but is installed on the machine and I would like to know two things.
Is it advisable to move the server from local to docker and keep the whole architecture "dockerized"?
How can I implement this using the nginx server in docker to have the same result ?

Get access to telegram api from docker compose through proxy

We have a server where we run different services in docker containers. The server is on the corporate network and does not have Internet access. We use a proxy to access the Internet. We collect images locally, where we have access to the Internet through a proxy, and then docker pull to our repository
Actually the question is: how to launch two new services using a docker compose that would have access to the Internet using a proxy?
Accordingly, simply trying to connect to a proxy in the code did not help, it failed to connect.
Passing the connection string to the proxy as an environment variable on startup didn't help either.

Remote HTTP Endpoint to Docker Application

I have a demo application running perfectly on my local environment. However, I would like to run the same application remotely by giving it a HTTP endpoint. My goal is to test the performance of the application.
How to give a HTTP endpoint to any multi container docker application?
The following is the Github repository link for the demo application
https://github.com/LonareAman/BankCQRS.git
Use docker-compose and handle containers based on what you need
One of your containers should be web server like nginx. And then bind your machine port to your nginx like 80:80
Then handle your containers in nginx and make a proxy to them
You can find some samples in https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/

GCP Kubernetes cannot connect to RabbitMQ server

I have a docker image on the google cloud platform that I would like to run. Part of this script attempts to connect to a RabbitMQ server (located in the same subnet). This does not work.
I've taken the following steps to try and solve it:
I have tried connecting to both the internal and external IP-address of the RabbitMQ server.
I have enabled VPC-native (alias IP)
I have checked I can connect to the internet from my docker image
I have checked that my docker image can connect to RabbitMQ when run locally
I have checked that the server can connect to the internal IP-address from the RabbitMQ server (by pinging it)
I think I probably have an incorrect setting in my kubernetes engine, but I've looked for quite some time and I cannot find it.
Does anybody know how to connect to a RabbitMQ server from a Kubernetes pod running in the Google Cloud Platform?

Access redis on host from inside docker container?

I have a host server that I'm deploying a dockerized Rails app on. The redis on the host server is not dockerized.
I'm trying to figure out how I can access the redis pub/sub on the host server from within the dockerized Rails app. The redis on the host server is configured to only be accessible from localhost.
Is there anyway for me to forward the pub/sub messages into the docker container? If it makes it easier, I don't really need to publish messages, only subcribe to read them.

Resources