api-docker | xBrowserSync API for Docker | REST library

First, the SQLALCHEMY_DATABASE_URI in database.py should match the user, password and database name suplied in Your docker-compose.yaml. Ensure that You are running docker-compose up with correct environ. In Your case, the environ for docker-compose up should be:

I have managed to get this working. For the benefits of others ill share my learnings:

I made a few small changes starting with my api function. Changing the function to the following:

It turns out unused images took 99% of the space allowed for images.

A. Let's go the big scale first.

At the time of writing Cloud Run instances can be set to a maximum of 1000 concurrency requests. And CPUs can be set to 4 vCPUs.

Going back to basics a bit. Cloud Run will span many instances, each will work individually, and each could handle the maximum allowed concurrency, so each could handle 1000 requests. If you set multiple CPUs you need to handle multi processes.

When we talk about so large number we need to be cautious. If your container is big enough in CPU/Memory terms to handle this traffic, you may want to use a process manager (gunicorn) to start several Uvicorn threads (workers), as your referenced images do. So you can use the docker container.

B. Being on small scale.

On the other hand if you set 1 vCPU and be single threaded, you don't need gunicorn for process manager. You still can have concurrency enabled but not on the top level, maybe at the lower level, that fits your 1 vCPU model, something like 80 requests for concurrency. In this situation you will have on large traffic, many instances started by Cloud Run, and you rely at Cloud Run to spawn as many instances as needed, which does really nice. It's like a Kubernetes on top of your simple container.

I would suggest start with single process, build a container that doesn't use the referenced container, and only swap B to version A, when you know there are benefits(costs wise) to have larger instances.

Our solution was a customer logger written in python that is referenced in a logging.conf file

logging.conf

If node is the only app that connects to postgre-db you can remove the networks, and expose the postgredb running port (5432). To connect to the db you can simply use the container name as host.

Connection String: "postgres://YourUserName:YourPassword@postgres-db:5432/YourDatabase";

"The AppSpec file for an Amazon ECS deployment specifies your task definition, container name, and container port."

Please refer to this article for more information - https://docs.aws.amazon.com/codedeploy/latest/userguide/tutorial-ecs-create-appspec-file.html

As your nginx.conf file :

server inconnect:5001; should be server inconnect1:5001;

And in docker compose file should use link from nginx container to inconnect1 application. (remove network on nginx container)

As we established in the comments section, your problem is not because of wrongly set up virtual environment, but it's worth mentioning the possible solution for others who might come across this question in future.

The problem with virtual env being invoked from other virtual env directory is a frequent symptom of copying virtual env directory from one place to another. This should be avoided! The reason behind that is the VIRTUAL_ENV variable hardcoded in [venv_dir]/bin/activate script. So, always make sure that this variable points to a valid directory.

In order to list packages from a virtual environment only, you need to use --local flag either for pip freeze or pip list. You can find this in the documentation:

-l, --local

If in a virtualenv that has global access, do not list globally-installed packages.

The key phrase is global access. The possible reason why pip keeps finding packages that are outside your virtual environment might be the PYTHONPATH and PATH environment variables. Check them. Whatever you have in those paths will be visible by pip.